Permalink
Browse files

Created settings.example, updated documentation to recommend copying …

…it to settings
  • Loading branch information...
boutell committed Jul 14, 2012
1 parent 5a43e2e commit 9cf9ac1ce28045e7c8491e52259287a54cd706db
Showing with 6 additions and 1 deletion.
  1. +1 −1 README.md
  2. +5 −0 settings.example
View
@@ -27,7 +27,7 @@ Although `sc-deploy` doesn't care where you install things, for easiest use of `
Configuration
=============
-Copy stagecoach to `/opt/stagecoach` on your staging server. Edit `/opt/stagecoach/settings` and make sure `USER` is set to the non-root user that web apps should run as. Then create the `/opt/stagecoach/apps` folder and `chown` that folder to that same non-root user.
+Copy stagecoach to `/opt/stagecoach` on your staging server. Copy `/opt/stagecoach/settings.example` to `/opt/stagecoach/settings` and make sure `USER` is set to the non-root user that your apps should run as. Then create the `/opt/stagecoach/apps` folder and `chown` that folder to the same non-root user. `nodeapps` is a nice name if you want to make a new user for node apps, but any user account can be used. Root is a bad choice for security reasons.
Additional configuration steps are covered under `sc-proxy`, below.
View
@@ -0,0 +1,5 @@
+# Currently must be /opt/stagecoach
+DIR=/opt/stagecoach
+# User to launch individual webapps as.
+# Since they do not listen on port 80 this need not be root
+USER=nodeapps

0 comments on commit 9cf9ac1

Please sign in to comment.