Public | Automated Build

Last pushed: 2 days ago
Short Description
Github auto build
Full Description


jam wit me

To run

Clone git repository
navigate to directory and run npm install
modify your hostfile to have localhost changed to (you can just add another field for
run npm run start-dev
from here on if you have any style changes or changes to public info you can just run npm run styles and then npm run start to shortcut the bundling.


Don't push to master unless we are shipping a new version. Only push to staging. When we are ready to ship a new version to production we will merge test and staging and then create a new staging branch to push to.

Create new feature branches off of staging and push to those, merge them with staging when complete and ship to staging.

Building and deploying

You should be on the staging branch, pull the existing staging branch and resolve any merge conflicts and then verify that it works, run the docker build commands, and push your docker build out to [docker-username]/staging. Then you should remote in to the digital ocean droplet, and stop the existing [username]/staging container start your recently pushed build.

Eventually we will have two separate droplets running each one, but for now we can just use separate containers.

Tips and tricks

If the hot reloading is requiring you to update a bunch of things you can save the state in local storage. Just change the key here.

componentDidMount() {
    window.onbeforeunload = () => this.saveState();
    this.setState(JSON.parse(window.localStorage.getItem('events') || '{}'))

  componentWillUnmount() {

  saveState() {
    window.localStorage.setItem('events', JSON.stringify(this.state));

Serving Node js over https requires constructing a server with the https module (in express 4)
Generate a cert with this method
It can be configured to serve on both http and https if you use the http module.

Docker Pull Command
Source Repository

Comments (0)