Hello,
It seems quite common for organizations to offer Linux servers (often
Debian) on which members can host their personal page (often mod_userdir).
This approach can have some drawbacks such as running PHP as each user
in a safe way is hard.
What do people here think of the following alternative:
* We have a reverse proxy listening on 80 and 443, it reverses
https://perso.example.com/USER/ to a socket in /home/USER/.page.socket
* The user has the choice to use any web server they want on this
socket. It can be uwsgi, Apache, Golang, NGINX...
* We propose a way to start (and stop) the user-side server with a
service manager looking for incoming requests on this socket.
This may sound complex, but would allow flexibility and simplicity for
users. It does not work because I believe Apache cannot listen on an
unix socket file.
Does anyone have better solutions or ideas to explore?
--
Alexandre
Volunteer in Crans student network organization (crans.org)
It seems quite common for organizations to offer Linux servers (often
Debian) on which members can host their personal page (often mod_userdir).
This approach can have some drawbacks such as running PHP as each user
in a safe way is hard.
What do people here think of the following alternative:
* We have a reverse proxy listening on 80 and 443, it reverses
https://perso.example.com/USER/ to a socket in /home/USER/.page.socket
* The user has the choice to use any web server they want on this
socket. It can be uwsgi, Apache, Golang, NGINX...
* We propose a way to start (and stop) the user-side server with a
service manager looking for incoming requests on this socket.
This may sound complex, but would allow flexibility and simplicity for
users. It does not work because I believe Apache cannot listen on an
unix socket file.
Does anyone have better solutions or ideas to explore?
--
Alexandre
Volunteer in Crans student network organization (crans.org)
Attached Files:
-
OpenPGP_signature (0.82 KB)