Skip to content
Browse files

* Pass arguments to forever in the correct order so the logging optio…

…ns work as intended

* Moved sc-deploy to a bin/ folder so it's reasonable to add to your PATH. This is where sc-rollback and sc-cleanup will live
* Finished up the upstart script, huzzah
  • Loading branch information...
1 parent 72cfe69 commit 0ab71aa4256f58fe53d2ff264c599b072741e4de @boutell boutell committed
Showing with 3 additions and 3 deletions.
  1. 0 { → bin}/sc-deploy
  2. +1 −1 example/deployment/start
  3. +2 −2 sc-proxy/upstart/stagecoach.conf
View
0 sc-deploy → bin/sc-deploy
File renamed without changes.
View
2 example/deployment/start
@@ -38,7 +38,7 @@ fi
# Run the app via 'forever' so that it restarts automatically if it fails
# Use `pwd` to make sure we have a full path, forever is otherwise easily confused
# and will stop every server with the same filename
-forever start `pwd`/server.js -o data/console.log -e data/error.log && echo "Site started"
+forever -o data/console.log -e data/error.log start `pwd`/server.js && echo "Site started"
# Run the app without 'forever'. Record the process id so 'stop' can kill it later.
# We recommend installing 'forever' instead for node apps. For non-node apps this code
View
4 sc-proxy/upstart/stagecoach.conf
@@ -13,7 +13,7 @@ start on startup
stop on shutdown
pre-start script
- source /opt/stagecoach/sc-proxy/sc-start-all
+ bash /opt/stagecoach/sc-proxy/sc-start-all
end script
script
@@ -21,5 +21,5 @@ script
end script
pre-stop script
- source /opt/stagecoach/sc-proxy/sc-stop-all
+ bash /opt/stagecoach/sc-proxy/sc-stop-all
end script

0 comments on commit 0ab71aa

Please sign in to comment.
Something went wrong with that request. Please try again.