Real men use AOLserver.
A fork of AOLserver still seem to be actively developed https://wiki.tcl-lang.org/page/NaviServer
Huh, TCL for web … Maybe I should dig up some old code …
Just use netcat and expect with a loose parse and timeout in your switch loop.
I think maybe I’d prefer a Ruby/Rack (and Roda) setup to nc/expect
I was trying to think of something as a worse extension of TCL, and expect is what came to mind.
You’re old as fuck, though, since you know what it is.
Web/TK?
Thanks!
I thought ARexx was bad, but now you make me want to make a lesstif render which outputs standard Xlib and is converted to gifs.
I like eggs.
Here’s direct links to compare configuration of different web servers :
Monkey
http://monkey-project.com/documentation/1.5/
H2O
https://h2o.examp1e.net/configure/quick_start.html
Lighttpd
https://redmine.lighttpd.net/projects/lighttpd/wiki/TutorialConfiguration
Apache
https://httpd.apache.org/docs/2.4/configuring.html
Litespeed
https://www.litespeedtech.com/docs/webserver/config
nginX
https://www.nginx.com/resources/wiki/start/topics/examples/full/
Caddy
https://caddyserver.com/tutorial/caddyfile
Cherokee
http://cherokee-project.com/doc/config_walkthrough.html
Hiawatha
https://www.hiawatha-webserver.org/howto/example_configuration
Another one is Tengine, it’s a fork of nginx with some other additions
I believe OpenBSD also have their own relayd/httpd
now …
Tengine has support for QAT, which is pretty cool.
Simply put : the SSL negotiation / encryption / decryption part can speed up 30 - 60%
Cutting your time to first byte considerably.
Lighty & PHP is a very good marriage, really.
It’s great for static content too.
In the past it would buffer large files in memory, leading to memory leaks, but that has been addressed a few years ago, now it uses temp files, while nginx (unlike Tengine) still buffers in memory.
Just install php-fpm, or different approach?
(wiki links pointed to dead site and old articles on building php4-cgi …)
Pretty straightforward … It’d be quicker to just install and read README.Debian than trying figure it out through their wiki/documentation …
Seems I will have to manually combine cert and key to combined file with Lighty, something like
cat /etc/letsencrypt/live/example.com/privkey.pem /etc/letsencrypt/live/example.com/cert.pem > /etc/letsencrypt/live/example.com/combined.pem
But how to automate that part
certbot
cron/systemd timer runs often, but will only renew if it’s less than 30 days or something (IIRC), Should probably make a job that checks for changes to cert, I guess.