what was the daemon doodad that actually lets non-root users register daemons? was it daemontools?
-
@eevee I like the .htaccess-like approach because the sysadmin can easily delegate URLs to ppl; make a directory, chown it to them, done.
Chris Siebenmann
@thatcks yeah but then you have a monster process doing like five kinds of delegation and supervision while claiming to be an "httpd"
-
-
@thatcks i would rather we had each user can just run its own web server (of their choosing!) and bind to some existing socket -
@thatcks then you don't need hacks like .htaccess and no one can take anyone else down with them -
@thatcks you also don't need stuff like mod_suexec! imo apache basically ruined this for everyone by building in stuff it shouldn't need
-
-
-
@eevee Without separate IPs, you need some central thing to route and forward incoming requests to the right user app. -
@thatcks right. the nginx idea i want to try is basically telling it to proxy *everything* to /var/www/$DOMAIN.sock or whatever -
@thatcks so all root needs to do is create that socket, once, and chown it to the appropriate user. anything without a socket will just fail
-
-
@eevee So for me it's just a question of how the central thing is told who owns what & where it gets forwarded. Per-dir config works nicely.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.