-
Notifications
You must be signed in to change notification settings - Fork 14
Deployment
timothyk7 edited this page Mar 15, 2015
·
40 revisions
used for continues integration and deployment of the app to heroku
- setup so when a developer pushes to a branch, will run gulp automation scripts and deploy to heroku
the pipeline that will deploy to dev and prod environments
Setup Commands
-
nvm install 0.10.25
nvm use 0.10.25
- used to setup nodejs environment, tells heroku to use this specific version of nodejs -
npm install
- used to install all required plugins from the package.json
Testing
-
gulp test
- used to run karma jasmine test from the 'test' folder
Deployment synchronized with guthub develop and master repo, will look for changes then deploy
-
Develop
- deploys develop branch to http://robobetty-dev.herokuapp.com
- when setting up to deploy to heroku, make sure you are a collaborator (for robobetty-dev). Then, add unique heroku api id from heroku. https://dashboard.heroku.com/account
-
Master
- deploys master branch to: http://robobetty.herokuapp.com http://ireceptionist.herokuapp.com
- when setting up to deploy to heroku, make sure you are a collaborator (for robobetty and ireceptionist). Then, add unique heroku api id from heroku. https://dashboard.heroku.com/account
Environment Variables
- N/A for deployment
the pipeline that will deploy to sandbox for deployment team to test
Setup Commands
-
nvm install 0.10.25
nvm use 0.10.25
- used to setup nodejs environment, tells heroku to use this specific version of nodejs -
npm install
- used to install all required plugins from the package.json
Testing
-
gulp test
- used to run karma jasmine test from the 'test' folder -
gulp build
- used to build code into minified/ uglified code [WIP]
Deployment synchronized with guthub develop and master repo, will look for changes then deploy
- Develop
- deploys develop branch to http://cse112-deployment-sandbox.herokuapp.com
- when setting up to deploy to heroku, make sure you are a collaborator (for cse112-deployment-sandbox). Then, add unique heroku api id from heroku. https://dashboard.heroku.com/account
Environment Variables
- N/A for deployment
where the application is hosted
###Currently Setup Heroku environments:
ireceptionist (robobetty)
- the environment for the production ready code
- the production ready code comes from robobetty-dev once the managers and architects believe it's ready
- has new relic and mongolab addons
robobetty-dev
- the environment currently in development
- this code has been confirmed by the managers and where QA will do basic testing before being pushed to production
- has new relic and mongolab addons
robobetty-test[1,2,3]
- mainly for developers to check that their code will work before pushing to the development environment
- has test1, test2, test3 environments for developers to choose which environment to test on
- has mongolab addon
cse112-deployment-sandbox
- mainly for deployment team to test deployment scripts on codeship and gulp scripts
- once checked off by the manager, will merge scripts into main develop branch
- has new relic and mongolab addons
Mongolab
- used to store mongo db
New Relic
- used for monitoring the current application in dev and prod environments