Repository navigation
Deploy Instructions
jSwanson99 edited this page Nov 23, 2020
·
9 revisions
Last Updated: June 29, 2017 This process requires the AWS EB CLI.
Please see the Wiki page for reviewing pull requests for more details.
- Navigate to local repo.
$ cd rSENSE
- Pull the latest version of master.
$ git pull upstream master
- Compile stylesheets & assets
rake assets:precompile
- Start the rails server
rails s
4) Old AWS Instructions: Switch to the dev environment.
$ eb use rsense-beanstalk-dev-env
5) Deploy.
$ eb deploy
5) If you need to run special commands, ssh into the machine.
$ eb ssh ... $ logout
## III. Testing
Everyone in the lab is a tester. The testing evaluation forms are as follows:<br>
1) [Basic tests](https://drive.google.com/open?id=1VE-mvK0zGWbIDM0rsABFp21OC_Oqs_i2XLMmz36M_Ec) are a standard set of procedures repeated every release.<br>
2) [Specific tests](https://dev.isenseproject.org/testing) encompass all new changes made to the website since the last release.
## IV. Post-testing
Go through testing results and make judgments on what to do next.
- Possibly create new bugs.
- Make any necessary fixes.
- Note when an issue failed testing. Determine whether this failed issue will hold back the release if it cannot be fixed on the spot. Also, remove the "In-Testing" tag from this issue.
- Close all issues marked “In-Testing” and passed testing.
## V. Push to Live
1) Create a new release on GitHub [here](https://github.com/isenseDev/rSENSE/releases) (NOTE: Do not complete this step until you are actually ready to release).<br><br>
2) Click Draft a new release.<br><br>
3) Enter Tag version, Release title, and a description.<br> As an example,
This release provides the following new features:
- Compass for maps
- Automatic suggestions for grouping your data in bar graphs
- Download charts as PNG images, PDF documents, in addition to SVG
- Updated Meet the Team Page
- Official iSENSE emails now have a more official-looking design
The following bugs were fixed:
- The Visualizations page no longer opens in a new tab
- Minor design changes
4) Click Publish Release when finished.<br><br>
5) Switch to the production environment.
$ eb use rsense-beanstalk-env
6) Deploy.
$ eb deploy
7) If you need to run special commands, ssh into the machine.
$ eb ssh ... $ logout
8) Poke fun at live to make sure stuff works.
9) Create a [news entry](https://isenseproject.org/news) containing the release description.
<hr>
#### Dev
[dev.isenseproject.org](https://dev.isenseproject.org/)
#### Live
[isenseproject.org](https://isenseproject.org/)
General
- New Developer Reference
- Setting up a Dev Environment
- The Scrum Board
- Git Reference
- Web Technology Reference
- Reviewing Pull Requests
-
Deploying
Misc
Security
Code Documentation