deploy on standard ports w/o root access about pad HOT 4 CLOSED

To be specific; the etherpad webservice would start with root access, bind to port 80 and quickly degrade itself to non-root.

from pad.

This is not done in most app-servers for security reasons, better to put all eggs in one basket - nginx or apache. Setting up forwarding using one of those isn't too hard.

from pad.

We will prepare an etherpad-proxy package which is provided by etherpad-authbind, etherpad-apache2 and etherpad-nginx to proxy from port 80 to the etherpad port.

Doing this for 443 would be to much work (certificate stuff) but if the user has the pattern how to proxy it will be easy for him to add the neccessary configuration options for ssl.

from pad.

Closing as nginx and apche + and https in nginx/apache both works really nice, no need for complicating the appserver itself.

from pad.