Op 04-01-16 om 21:58 schreef Robert Zehnder:
I would handle it the way any other server application would be deployed
(ie, Tomcat, Nginx, Apache). I would say start the process with a
restricted user (running any server process as root i*s bad*). So in
this case perhaps create a new user for the app to use and ensure that
user has read access and write access to the project directory as required.
Additionally, the chroot npm does some checking of permissions and is a
good way to sandbox your application (in combination with
child_process.fork).
-Tim
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups "nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/568AF1DA.5050209%40netsend.nl.
For more options, visit https://groups.google.com/d/optout.
