Hi there!
Last week Mohammed wrote that he can't wait to test out perl 5.40. In response Michiel Beijen wrote a blog post explaining how you can already try 5.39.10, using plenv. I love this!
As you might know a while ago I stopped using mailman for the Perl Weekly and now both the subscription and unsubscription process is done by sending me an email that I read and process manually. This gives an excellent opportunity to the new subscribers to introduce themselves and even to mention the subjects that are interested in.
As the Perl Weekly is a news aggregator I am going to share some of the items in his mail hoping that some of you will write blog posts covering some of the issues.
After a long break from Perl, I'm looking for best current practice on building a website for a cycling club. So I'm curious about the full stack (for collaborative dev, integration, and public deployment) the architecture (MVC (Dancer2 or Mojolicious) & DB), and frameworks for Plack/PSGI, JavaScript, unit and acceptance testing, and OO, for example. Also, what collaborative tools to use for Scrum/Kanban collaboration, and source control, CI and CD. To start with, I am hunting around for best practice on a dev Webserver and client, and, later, a public web hosting server.
This was my response: To respond to your questions: I personally was using Dancer a lot, but Mojolicious seems to have slightly more development activity. For CI I use either GitHub Actions or GitLab pipelines depending on which git hosting service the project uses. I rent a server at Linode, but I have converted many of my sites to be static using some Static Site Generator and then I host them on GitHub pages.
I hope you'll have more detailed answer.
Actually, in this edition we have a post by Dave Cross on Deploying Dancer Apps already responding to part of the questions. This is how time-machine works.
Have a nice week!
Gabor Szabo
|