home.social

#dancer2 — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #dancer2, aggregated by home.social.

  1. Playing around with #starman and #dancer2, since apparently no one uses #perlcgi any more.

    If anyone can recommend some beginner resources, I'd appreciate it, specifically around form processing and DB interactions.

    #perl #selfhosting #selfhosted #webcrafting #webserver

  2. Playing around with #starman and #dancer2, since apparently no one uses #perlcgi any more.

    If anyone can recommend some beginner resources, I'd appreciate it, specifically around form processing and DB interactions.

    #perl #selfhosting #selfhosted #webcrafting #webserver

  3. Playing around with #starman and #dancer2, since apparently no one uses #perlcgi any more.

    If anyone can recommend some beginner resources, I'd appreciate it, specifically around form processing and DB interactions.

    #perl #selfhosting #selfhosted #webcrafting #webserver

  4. Playing around with #starman and #dancer2, since apparently no one uses #perlcgi any more.

    If anyone can recommend some beginner resources, I'd appreciate it, specifically around form processing and DB interactions.

    #perl #selfhosting #selfhosted #webcrafting #webserver

  5. Playing around with #starman and #dancer2, since apparently no one uses #perlcgi any more.

    If anyone can recommend some beginner resources, I'd appreciate it, specifically around form processing and DB interactions.

    #perl #selfhosting #selfhosted #webcrafting #webserver

  6. I'm at the point in my #Perl #Dancer2 journey where I'm spending more time chasing bugs in core modules than my own code 😞

    The database modules have two long-standing bugs that you'd expect most users to hit:

    1. Authentication using a db does not refresh stale handles, so you can't login.

    2. Multiple db connections don't inherit the application charset setting.

    These bugs have existed for ten years with fixes available. Is no one actually using Dancer2 or are we all patching locally?

  7. I'm at the point in my #Perl #Dancer2 journey where I'm spending more time chasing bugs in core modules than my own code 😞

    The database modules have two long-standing bugs that you'd expect most users to hit:

    1. Authentication using a db does not refresh stale handles, so you can't login.

    2. Multiple db connections don't inherit the application charset setting.

    These bugs have existed for ten years with fixes available. Is no one actually using Dancer2 or are we all patching locally?

  8. I'm at the point in my #Perl #Dancer2 journey where I'm spending more time chasing bugs in core modules than my own code 😞

    The database modules have two long-standing bugs that you'd expect most users to hit:

    1. Authentication using a db does not refresh stale handles, so you can't login.

    2. Multiple db connections don't inherit the application charset setting.

    These bugs have existed for ten years with fixes available. Is no one actually using Dancer2 or are we all patching locally?

  9. I'm at the point in my #Perl #Dancer2 journey where I'm spending more time chasing bugs in core modules than my own code 😞

    The database modules have two long-standing bugs that you'd expect most users to hit:

    1. Authentication using a db does not refresh stale handles, so you can't login.

    2. Multiple db connections don't inherit the application charset setting.

    These bugs have existed for ten years with fixes available. Is no one actually using Dancer2 or are we all patching locally?

  10. I'm at the point in my #Perl #Dancer2 journey where I'm spending more time chasing bugs in core modules than my own code 😞

    The database modules have two long-standing bugs that you'd expect most users to hit:

    1. Authentication using a db does not refresh stale handles, so you can't login.

    2. Multiple db connections don't inherit the application charset setting.

    These bugs have existed for ten years with fixes available. Is no one actually using Dancer2 or are we all patching locally?

  11. I’ve had a fun day converting my #Perl #Dancer2 application to use #SQLite instead of MySQL, which not only suits the size and expected use of the application better, but gave me the opportunity to get rid of MySQLisms. It has become so much easier to work locally with Dancer, allowing a lot of schema and view changes very quickly, so I can see the relationships between A. C. Michael’s paintings much faster. #art #CatalogueRaisonné

  12. I’ve had a fun day converting my #Perl #Dancer2 application to use #SQLite instead of MySQL, which not only suits the size and expected use of the application better, but gave me the opportunity to get rid of MySQLisms. It has become so much easier to work locally with Dancer, allowing a lot of schema and view changes very quickly, so I can see the relationships between A. C. Michael’s paintings much faster. #art #CatalogueRaisonné

  13. I’ve had a fun day converting my #Perl #Dancer2 application to use #SQLite instead of MySQL, which not only suits the size and expected use of the application better, but gave me the opportunity to get rid of MySQLisms. It has become so much easier to work locally with Dancer, allowing a lot of schema and view changes very quickly, so I can see the relationships between A. C. Michael’s paintings much faster. #art #CatalogueRaisonné

  14. I’ve had a fun day converting my #Perl #Dancer2 application to use #SQLite instead of MySQL, which not only suits the size and expected use of the application better, but gave me the opportunity to get rid of MySQLisms. It has become so much easier to work locally with Dancer, allowing a lot of schema and view changes very quickly, so I can see the relationships between A. C. Michael’s paintings much faster. #art #CatalogueRaisonné

  15. I’ve had a fun day converting my #Perl #Dancer2 application to use #SQLite instead of MySQL, which not only suits the size and expected use of the application better, but gave me the opportunity to get rid of MySQLisms. It has become so much easier to work locally with Dancer, allowing a lot of schema and view changes very quickly, so I can see the relationships between A. C. Michael’s paintings much faster. #art #CatalogueRaisonné

  16. I have a #Perl #Dancer2 application that uses a database. For non-authenticated routes, db connections that timeout are reconnected automatically. Nice. However, authenticated routes, which also require the db, are not reconnected because Dancer2::Plugin::Auth::Extensible::Provider::Database caches a stale handle.

    Luckily, a pull request has been outstanding for 8 years, so I can patch locally. I hope this isn't a bellwether for Dancer2 vivacity in general. [edit: typo]

  17. I have a #Perl #Dancer2 application that uses a database. For non-authenticated routes, db connections that timeout are reconnected automatically. Nice. However, authenticated routes, which also require the db, are not reconnected because Dancer2::Plugin::Auth::Extensible::Provider::Database caches a stale handle.

    Luckily, a pull request has been outstanding for 8 years, so I can patch locally. I hope this isn't a bellwether for Dancer2 vivacity in general. [edit: typo]

  18. I have a #Perl #Dancer2 application that uses a database. For non-authenticated routes, db connections that timeout are reconnected automatically. Nice. However, authenticated routes, which also require the db, are not reconnected because Dancer2::Plugin::Auth::Extensible::Provider::Database caches a stale handle.

    Luckily, a pull request has been outstanding for 8 years, so I can patch locally. I hope this isn't a bellwether for Dancer2 vivacity in general. [edit: typo]

  19. I have a #Perl #Dancer2 application that uses a database. For non-authenticated routes, db connections that timeout are reconnected automatically. Nice. However, authenticated routes, which also require the db, are not reconnected because Dancer2::Plugin::Auth::Extensible::Provider::Database caches a stale handle.

    Luckily, a pull request has been outstanding for 8 years, so I can patch locally. I hope this isn't a bellwether for Dancer2 vivacity in general. [edit: typo]

  20. I have a #Perl #Dancer2 application that uses a database. For non-authenticated routes, db connections that timeout are reconnected automatically. Nice. However, authenticated routes, which also require the db, are not reconnected because Dancer2::Plugin::Auth::Extensible::Provider::Database caches a stale handle.

    Luckily, a pull request has been outstanding for 8 years, so I can patch locally. I hope this isn't a bellwether for Dancer2 vivacity in general. [edit: typo]

  21. I had a really positive surprise this morning. My 14-year old has been teaching himself all sorts of computing skills since the start of the summer, so I asked him to look at my catalogue raisonné #Perl app, which I’ve been coding using #Dancer2. He not only critiqued the web page layout (“those links are in the wrong place: I didn’t even see them at first”) and spotted several inconsistencies in the menus, but made me think about the data underlying the catalogue itself. 1/2

  22. I had a really positive surprise this morning. My 14-year old has been teaching himself all sorts of computing skills since the start of the summer, so I asked him to look at my catalogue raisonné #Perl app, which I’ve been coding using #Dancer2. He not only critiqued the web page layout (“those links are in the wrong place: I didn’t even see them at first”) and spotted several inconsistencies in the menus, but made me think about the data underlying the catalogue itself. 1/2

  23. I had a really positive surprise this morning. My 14-year old has been teaching himself all sorts of computing skills since the start of the summer, so I asked him to look at my catalogue raisonné #Perl app, which I’ve been coding using #Dancer2. He not only critiqued the web page layout (“those links are in the wrong place: I didn’t even see them at first”) and spotted several inconsistencies in the menus, but made me think about the data underlying the catalogue itself. 1/2

  24. I had a really positive surprise this morning. My 14-year old has been teaching himself all sorts of computing skills since the start of the summer, so I asked him to look at my catalogue raisonné #Perl app, which I’ve been coding using #Dancer2. He not only critiqued the web page layout (“those links are in the wrong place: I didn’t even see them at first”) and spotted several inconsistencies in the menus, but made me think about the data underlying the catalogue itself. 1/2

  25. I had a really positive surprise this morning. My 14-year old has been teaching himself all sorts of computing skills since the start of the summer, so I asked him to look at my catalogue raisonné #Perl app, which I’ve been coding using #Dancer2. He not only critiqued the web page layout (“those links are in the wrong place: I didn’t even see them at first”) and spotted several inconsistencies in the menus, but made me think about the data underlying the catalogue itself. 1/2

  26. Having used a ‘standard’ web host for over 25 years (Apache, MySQL, Perl CGI), I’ve now rebuilt my application in #Perl #Dancer2, which was a joy and speeded up things no end for me on localhost. Now it's time to consider deployment and I don't know where to do it. Given the likely low traffic, I'm tempted to run it entirely on my home machine. But, to paraphrase a famous maxim about lawyers, does someone who sysadmins their own site at home have a fool for a client?

  27. Having used a ‘standard’ web host for over 25 years (Apache, MySQL, Perl CGI), I’ve now rebuilt my application in #Perl #Dancer2, which was a joy and speeded up things no end for me on localhost. Now it's time to consider deployment and I don't know where to do it. Given the likely low traffic, I'm tempted to run it entirely on my home machine. But, to paraphrase a famous maxim about lawyers, does someone who sysadmins their own site at home have a fool for a client?

  28. Having used a ‘standard’ web host for over 25 years (Apache, MySQL, Perl CGI), I’ve now rebuilt my application in #Perl #Dancer2, which was a joy and speeded up things no end for me on localhost. Now it's time to consider deployment and I don't know where to do it. Given the likely low traffic, I'm tempted to run it entirely on my home machine. But, to paraphrase a famous maxim about lawyers, does someone who sysadmins their own site at home have a fool for a client?

  29. Having used a ‘standard’ web host for over 25 years (Apache, MySQL, Perl CGI), I’ve now rebuilt my application in #Perl #Dancer2, which was a joy and speeded up things no end for me on localhost. Now it's time to consider deployment and I don't know where to do it. Given the likely low traffic, I'm tempted to run it entirely on my home machine. But, to paraphrase a famous maxim about lawyers, does someone who sysadmins their own site at home have a fool for a client?

  30. Having used a ‘standard’ web host for over 25 years (Apache, MySQL, Perl CGI), I’ve now rebuilt my application in #Perl #Dancer2, which was a joy and speeded up things no end for me on localhost. Now it's time to consider deployment and I don't know where to do it. Given the likely low traffic, I'm tempted to run it entirely on my home machine. But, to paraphrase a famous maxim about lawyers, does someone who sysadmins their own site at home have a fool for a client?

  31. 🎉 Dancer2 2.0.0 đã chính thức ra mắt! Cập nhật lớn cho framework web Perl này, với sự đóng góp từ nhiều tác giả. Cùng khám phá tính năng mới và tham gia thử thách lập trình hàng tuần để nhận giải thưởng! 💻✨

    #Perl #Dancer2 #LậpTrình #Coding #Programming #ViệtNam #TechNews

    dev.to/szabgab/perl-weekly-739

  32. 🎉 Dancer2 2.0.0 đã chính thức ra mắt! Cập nhật lớn cho framework web Perl này, với sự đóng góp từ nhiều tác giả. Cùng khám phá tính năng mới và tham gia thử thách lập trình hàng tuần để nhận giải thưởng! 💻✨

    #Perl #Dancer2 #LậpTrình #Coding #Programming #ViệtNam #TechNews

    dev.to/szabgab/perl-weekly-739

  33. @domm Thanks a lot for describing it - I'm currently trying to build something similar with a #Dancer2 app and a #PostgreSQL DB. I thought about integrating git somewhere in the publishing process, but couldn't think of a propper way yet...

  34. @domm Thanks a lot for describing it - I'm currently trying to build something similar with a #Dancer2 app and a #PostgreSQL DB. I thought about integrating git somewhere in the publishing process, but couldn't think of a propper way yet...

  35. @domm Thanks a lot for describing it - I'm currently trying to build something similar with a #Dancer2 app and a #PostgreSQL DB. I thought about integrating git somewhere in the publishing process, but couldn't think of a propper way yet...

  36. I’ve spent three days or so experimenting with #Perl #Dancer2 and it has been great fun. I’ve taken my current project, which is Perl, CGI, Template Toolkit and MySQL and remodelled it with Dancer2, using Plack for local serving. I spent the first two days simply reading and re-reading the Dancer2 manual and FAQ to get a big picture in my head, allowing quite a lot to whoosh me, and then sat down. This is going to be a lot smaller and faster than my old CGI apps, clearly.

  37. I’ve spent three days or so experimenting with #Perl #Dancer2 and it has been great fun. I’ve taken my current project, which is Perl, CGI, Template Toolkit and MySQL and remodelled it with Dancer2, using Plack for local serving. I spent the first two days simply reading and re-reading the Dancer2 manual and FAQ to get a big picture in my head, allowing quite a lot to whoosh me, and then sat down. This is going to be a lot smaller and faster than my old CGI apps, clearly.

  38. I’ve spent three days or so experimenting with #Perl #Dancer2 and it has been great fun. I’ve taken my current project, which is Perl, CGI, Template Toolkit and MySQL and remodelled it with Dancer2, using Plack for local serving. I spent the first two days simply reading and re-reading the Dancer2 manual and FAQ to get a big picture in my head, allowing quite a lot to whoosh me, and then sat down. This is going to be a lot smaller and faster than my old CGI apps, clearly.

  39. I’ve spent three days or so experimenting with #Perl #Dancer2 and it has been great fun. I’ve taken my current project, which is Perl, CGI, Template Toolkit and MySQL and remodelled it with Dancer2, using Plack for local serving. I spent the first two days simply reading and re-reading the Dancer2 manual and FAQ to get a big picture in my head, allowing quite a lot to whoosh me, and then sat down. This is going to be a lot smaller and faster than my old CGI apps, clearly.

  40. I’ve spent three days or so experimenting with #Perl #Dancer2 and it has been great fun. I’ve taken my current project, which is Perl, CGI, Template Toolkit and MySQL and remodelled it with Dancer2, using Plack for local serving. I spent the first two days simply reading and re-reading the Dancer2 manual and FAQ to get a big picture in my head, allowing quite a lot to whoosh me, and then sat down. This is going to be a lot smaller and faster than my old CGI apps, clearly.

  41. Hmm... I wonder if I could switch from hugo to a Dancer2 app for my personal blog...

    (Hugo is already a great step in the right direction from wordpress, but I still had the feeling that it is a little bit bloated...)

    #hugo #perl #Dancer2

  42. Hmm... I wonder if I could switch from hugo to a Dancer2 app for my personal blog...

    (Hugo is already a great step in the right direction from wordpress, but I still had the feeling that it is a little bit bloated...)

    #hugo #perl #Dancer2

  43. @getimiskon @segnwrisastoika Here’s a good article on current alternatives to the old #Perl CGI.pm module: metacpan.org/pod/CGI::Alternat

    tl;dr: You can write less code and eventually scale up to handle more traffic if you use a framework like #Mojolicious or #Dancer2. But if you must stick to #CGI, consider metacpan.org/pod/CGI::Tiny

    And if you haven't yet, follow chirp.social/@Perl to talk with nearly 500 other Perl users across the fediverse.

  44. @getimiskon @segnwrisastoika Here’s a good article on current alternatives to the old #Perl CGI.pm module: metacpan.org/pod/CGI::Alternat

    tl;dr: You can write less code and eventually scale up to handle more traffic if you use a framework like #Mojolicious or #Dancer2. But if you must stick to #CGI, consider metacpan.org/pod/CGI::Tiny

    And if you haven't yet, follow chirp.social/@Perl to talk with nearly 500 other Perl users across the fediverse.