@vandys @randomgeek @codinghorror As a #Perl hacker I will never besmirch #CGI as a standard or for light-use web scripts, but a lot of sins were committed with the two.

These days the done thing is to use #PSGI and a framework like #Mojolicious or #Dancer2 in a persistent app server. You don’t have to write nearly as much code, either. https://plackperl.org

The #Plack middleware can even run your code as a CGI or #FastCGI script if you reallly want.

ELI10 What the heck is #FastCGI

#PHP

@freyfogle #CGI’s bad rap came not from its programming model, but from its execution model of spawning a new process apart from the web server for every request. #FastCGI mitigated that by spinning up a separate persistent server that handles requests over and over again without forking, communicating with the web server over a socket, pipe, or TCP. It’s the same model as any other web application server.

@simon @js @berkes I have fond memories of a bespoke #FastCGI CRUD app I made in the mid-2000s. I got to choose every single component down to the bug tracker because I was a dev team of one, but I made sure there was both a stack and a process I could hand off so I could walk away when the project was over.

@sirber @rasmus all other features remain the same. #http vs #fastcgi is just transport protocol, not changing any logic. But by supporting http, you can plug it into various http-based loadbalancers/ingress-controllers out-of-the-box

Lots of chat around #php 8.2 release. One single feature (in two steps) will completely change the game:
1. Make php-fpm talk http (instead of outdated #fastcgi ) - also support static assets: removes any need for nginx sidecars, future proofing containerization.
2. Add new fpm mode: persistent. This means apps might break but this will ultimately put PHP performance wise back into competition with #python and even #golang @rasmus wdyt?

#phpfpm #unixsocket #fastcgi #nginx #pixelfed #ubuntu

I am preparing to host a Pixelfed instance and got stuck at nginx available site configuration. I used unixsocket for redis and not sure if I have to use unixsocket for fastcgi too.
Would it be fine if I set "fastcgi_pass localhost:9000;" rather than "fastcgi_pass Unix:/run/php-fpm/php-fpm.sock;" ?

I am asking because I couldn't locate php-fpm.sock or php-fpm8.1.sock anywhere in the system.

The more I struggle with #WebAppDeployment the more I understand why #GoLang :go_gopher: was designed to always produce #StaticBinaries with their own embedded webserver instead of using #FastCGI or whatever.

🚢 New minor #release v3.1.6 of hollodotme/fast-cgi-client, adding compatibility with PHP 8.1 #PHP #OSS #FastCGI #FPM
👉 https://github.com/hollodotme/fast-cgi-client

My #slides of today's talk about #FastCGI Client at the #OnlinePHPConference are up on speakerdeck. Thank you @thePHPcc@twitter.com for having me, thanks to all attendees for listening.
👉 https://speakerdeck.com/hollodotme/fastcgi-client-a-sync-requests-and-reactive-responses-with-php-fpm

#PHP #OSS

🚢 New #release v3.1.4 of hollodotme/fast-cgi-client is available - Adds compatibility with #PHP8 - https://github.com/hollodotme/fast-cgi-client/releases/tag/v3.1.4
#PHP #OSS #FastCGI

Lesson learned for #nextcloud #nginx #fastcgi and #php-fpm

set
fastcgi_buffering off
in nginx config to avoid directory-zip-download stopping with unfinished transfer and http status 200 after (in my case) 30sec

🚢 New #release v3.1.3 of hollodotme/fast-cgi-client is out - #Bugfix: broken sockets were not removed from internal collection after writing a request failed. Thanks @TobiasNyholm@twitter.com for the pointer! Also polished some code & tests. #PHP #FastCGI #OSS - https://github.com/hollodotme/fast-cgi-client/tree/v3.1.3

🚢 New #release v3.1.0 of hollodotme/fast-cgi-client is out. New feature allowing to compose url-encoded, multipart form-data (file uploads), JSON data & custom request contents with more ease. Have a look at the docs: https://github.com/hollodotme/fast-cgi-client#request-contents
#PHP #OSS #FastCGI

🚢 A new version v3.0.1 of hollodotme/fast-cgi-client is out. This release brings compatibility with #PHP 7.4. Thank you @themsaid@twitter.com for your contribution! #FastCGI #OSS

https://github.com/hollodotme/fast-cgi-client

🐣 A new #release v3.0.0 of hollodotme/fast-cgi-client is available. Coming with no additional features (compared to since 3.0.0-beta) but internal improvements. Please read the CHANGELOG for migrating from v2.x to v3.x. #PHP #OSS #FastCGI #Client #Lib

https://github.com/hollodotme/fast-cgi-client/blob/v3.0.0/CHANGELOG.md

🦋New version v3.0.0-beta of hollodotme/fast-cgi-client has been #released - Allows to send requests to different servers using ONE client instance, improves semantics of public api & docs - ⚠️BC breaks - please test & report issues! #PHP #OSS #FastCGI
https://github.com/hollodotme/fast-cgi-client/blob/v3.0.0-beta/CHANGELOG.md

🚢 A new version v0.2.0 of hollodotme/fast-cgi-proxy has been #released - Adds new features for #FastCGI #cluster requests & cluster status retrieval. It includes several improvements & some BC breaks. Thank you @mikesoule@twitter.com for the inspiration! 😊
https://github.com/hollodotme/fast-cgi-proxy/tree/v0.2.0

#Bugfix #release v2.7.1 of hollodotme/fast-cgi-client - Fixes a bug that could cause infinite retries/re-uses of broken socket connections in particular cases.

#OSS #PHP #FastCGI #Library

https://github.com/hollodotme/fast-cgi-client

🚀Version 2.7.0 of hollodotme/fast-cgi-client has been released. The client now automatically re-uses idle connections on successive requests. That can improve performance & use less resources (depending on use-case).

#OSS #PHP #FastCGI #Library

https://github.com/hollodotme/fast-cgi-client