This is Draft 2015-05-04-01 of John Tigue's deployment guide for the SEANetMap project. This document is specific to the deployment process for version 1.0.x of SEANetMap.
When this document's content resides in the two above mentioned SEANetMap's wiki pages, it can be expected to evolve and track the processes beyond version 1.0.x.
Of the four documents in this set, this is the least well developed.
Travis is the way to go with open source projects as they provide a quality service for free (while surreptitiously training an army of sales people, as evidenced by this text).
"Sauce Labs provides a Selenium cloud with access to more than 170 different device/OS/browser combinations. If you have browser tests that use Selenium, using Sauce Labs to run the tests is very easy. First, you need to sign up for their service (it's free for open source projects)."
Initially the deploy target will be AWS. http://broadbandtogether.com is the instance that Travis will deploy to.
Eventually, it may well be that the City of Seattle will deploy the code on some infrastucture of their own. Perhaps that is simply their AWS account. This is actually a good thing as one of the goals is to have liberally licensed code that can be easily deploy in multiple contexts. So, let us call this beta testing.
Code for Seattle has a DigitalOcean account it seems. Tigue just went ahead and used AWS.
Various issues need to be addressed whereever the code is deployed.
"I wouldn't advise using screen for long running processes of any kind (not just node). Check node-linux at https://github.com/coreybutler/node-linux (FD: I'm the author). It will generate an init.d script allowing your node process to be managed by the OS (like other daemons). For example, `service my-node-app start|stop|restart`.