#mojolicious — Public Fediverse posts

How to deploy a #Mojolicious web app to shared web hosting with Apache and CGI?

I’m having problems configuring ".htaccess" so that all pages are transparently handled by myapp.pl as a CGI script without revealing the CGI path and without breaking links in the app.

See here for details:
https://serverfault.com/questions/1190950/setup-mojolicious-app-transparently-via-cgi-with-apache-mod-rewrite

#httpd #ApacheHttpd #CGI #Perl

@ferki @verzulli If I understand your requirements correctly, you could install a #perl version with #perlbrew on your local machine, install your required modules with #cpanm and provided libraries match between your dev and prod machines you can just copy the perl directory and run the perl with full path in the new location.
If there is a library mismatch you are in a bit of pain to get it to work no matter what you do.
May I suggest you build the restapi with #mojolicious?

OpenFaaS Perl Mojolicious template - https://github.com/tschaefer/openfaas-perl-mojo-template
#openfaas #perl #mojolicious

I think about 2 years ago I had a long thread over here about updating my 10+ year old SPA (#backbonejs, #javascript, #perl, #Mojolicious) to a MPA using just #htmx for frontend interactivity.

Well, I've been way too busy to even start any of that! But, in the last couple of days I decided to go for a hybrid approach. I've added some htmx components to my single page application. My app's dashboard finally provides me with some interesting reports, powered by htmx.

That should do for now :-).

@[email protected] I still have a couple of SPA’s to manage that are about 9-10 years old. Written in #CoffeeScript 1 (not too bad) and #BackboneJS with a #Perl #Mojolicious backend.

Getting to run the JS dev stuff and keeping it up to date, or rather working with a newer Node version is challenging. Looking back it being a SPA doesn’t do much for 85% of these apps. I should’ve used some #jQuery instead for the interactive parts. That way I could’ve moved to #htmx without any issue.

Like I said, this stack of #perl, #Mojolicious, #MySQL, #CoffeeScript, #BackboneJS and #Bootstrap has served me well this past decade. I've got several business critical webapps running in it.

The backend stays. The frontend gets replaced by mostly plain #HTML with #htmx and #TailwindCSS. This makes development a lot faster: less context switching as most of it is done inside HTML templates. Added but very nice bonus: less complicated and error prone build pipeline!

END

Trying to add some new stuff this week made me realise: I don't enjoy working on this. It has nothing to do with the backend though. I'll always love #perl and #Mojolicious. Both very stable and this past decade I had very little issues with upgrading if any at all.

The part of the stack that needs replacement is the frontend. It's one big #SPA (single page application) which means a bunch of HTTP JSON endpoints and #Backbonejs + #CoffeeScript + #Mustache taking care of the client side.

The webapp is written in #perl with #Mojolicious for the backend powered by #MySQL.

For frontend I went with #Backbonejs and #CoffeeScript. The state and support of modern #JavaScript features was limited back then, dare I say cumbersome. I also enjoyed CoffeeScript, even though I don't like #Python ;-). To make it look half decent I went with #Bootstrap as a CSS framework, but hardly any customisations.

For development I used #Vagrant with #VirtualBox, but since 4-5 years I moved to #Docker.

@ology You might also consider creating your own module in the Mojolicious::Command::Author::generate namespace. There are a couple dozen on #CPAN already, maybe one is close to your needs? https://metacpan.org/search?q=module%3AMojolicious%3A%3ACommand%3A%3AAuthor%3A%3Agenerate
@Perl @mojolicious #Perl #Mojolicious #MetaCPAN #WebDev

@Perl @kraih just released v9.31 of #Mojolicious, the popular #Perl real-time #WebDev framework. It contains important security fixes as well as a few other bug fixes—everyone should upgrade!
Announcement: https://fosstodon.org/@mojolicious/109548887384460555
Changes and documentation on #MetaCPAN: https://metacpan.org/release/SRI/Mojolicious-9.31
README with installation instructions: https://metacpan.org/release/SRI/Mojolicious-9.31/source/README.md

Follow @mojolicious to stay up to date with more news!

Cette fois-ci, il se sera écoulé moins d’un an entre deux versions majeu­res… bon, ok, il s’est passé 9 mois… bon, ok, la liste des modi­fi­ca­tions n’est pas énor­me… 😅

Et pour­tant ! Et pour­tant, c’est une version rela­ti­ve­ment impor­tante.

En effet, il est main­te­nant possible de faire zipper par Lufi vos fichiers avant de les envoyer. Cela veut dire que plutôt que de four­nir 10 liens diffé­rents à vos corres­pon­dants, il est possible de n’en four­nir qu’un seul. Voyez plutôt :

(télé­char­ger la vidéo)

La deuxième modi­fi­ca­tion concerne plutôt les entre­prises et autres struc­tures utili­sant l’au­then­ti­fi­ca­tion LDAP : un utili­sa­teur connecté pourra invi­ter une personne n’ayant pas de compte LDAP à venir dépo­ser des fichiers sur Lufi pour les lui trans­mettre. Cette fonc­tion­na­lité a été finan­cée par la société TECH’ad­van­tage 😘

Je vous laisse avec cette varia­tion en rouge de l’artwork que j’avais commandé à Soniop l’an­née dernière, toujours en CC-BY-SA, (fichier source Photo­shop).

NB : il est à noter que cette nouvelle version béné­fi­cie des correc­tions de bugs récentes que j’ai pu appor­ter à Lufi ces derniers jours : voir les listes de modi­fi­ca­tions des versions 0.03.6 et 0.03.7.

Liens :

#artwork #lufi #mojolicious #sonio

https://fiat-tux.fr/2019/08/05/lufi-0-04-est-sorti/