Proposal for new build process

[remy]

Brain dump of ideas

• webhook looks out for new tags
• new tag = git pull
• git clone jsbinrepo into /WWW/deploy (at specific tag)
• runs npm install to update any package.json changes
• run grunt build
• if all exits okay then...
• renames /WWW/jsbin to /WWW/jsbin-old
• renames /WWW/deploy to /WWW/jsbin
• restarts jsbin service
• restart email gets a subject (that can also be defined by the user via the cli)

Note that sudo may be required for some/all of this.

Should email/IRC a report back.

[dannyhope]

A bell should ring out across the land

[remy]

Update on process.

Instead of renaming the directories:

• git clone <repo> jsbin-<tag>
• ::run build process::
• update a symlink called jsbin to point to the newly cloned repo

The result, a faster deploy to production process and the resulting ls shows:

jsbin-3.17.3/
jsbin-3.17.2/
jsbin -> jsbin-3.17.3

[remy]

Extra requests:

1. Automatically compare package deps against previous version, and copies across if they're the same (or maybe copied across anyway, then does npm install ... but this might cause permission issues if we run manually)
2. deploy latest works out the latest tag and does the rest.

[remy]

2nd version of deploy script: https://github.com/jsbin/production/blob/master/usr/local/bin/deploy now in use in production.

Features to add:

• Automatic tag webhook -> deploy
• Restart jsbin
• Management of old folders
• Tweet with version and compare url