Updating version

[nicolaspe]

We just tried updating the instance I had setup, but ran into many issues.

• I had customized the intro.ejs and app.css files, which led to issues when pulling the repo

• A lot of files are locked under permission barriers, so I had to use sudo git add -A, sudo git stash, etc...

• Also, I had to configure the git config --global user.name and git config --global user.email on the server machine

• I had no problem with the make backup for the db, but I couldn't do the make migrate later. Later I found the pm2 stop all command and got it to "work".

  $ pm2 stop organizer.network
  $ cd db/
  $ make migrate
  $ cd ..
  $ pm2 start all

• "work" is in quotation marks because now the instance doesn't work, it gives me a 502 message

  • I used pm2 start all and it says [PM2] Process successfully started, but it I check again it says errored

Any ideas on why it's not working?

P.S: I think next step will be writing a small "How to: update your instance" guide with @doodybrains and @Hbentzur

[dphiffer]

I would try two things:

• pm2 logs should show you recent log messages
• you could also try starting up the instance manually and see if any errors get reported: npm start

Otherwise, what you're describing sounds familiar to me. there are a few different things here:

• Need documentation for upgrading a running instance
• Make upgrading easier: add a maintenance mode, to free up the database connection (which blocks make migrate)
• Add new customization options? fwiw I am changing how intro.ejs works in v0.1.1.

Something that changed in release v0.1.0 is that there's a new file called ecosystem.config.js that controls how pm2 operates. The upshot is, instead of pm2 start organizer.network.js or pm2 start app.js you can just do pm2 start.

[dphiffer]

Also, thanks for the PR!

[dphiffer]

Added in v0.1.1:

• NODE_ENV=maintenance npm start starts the app in maintenance mode (no db connection)
• New script: bin/upgrade.sh to automate the upgrade process