Continuous deployment for xdai.io

[TimDaub]

Scope

• Currently the burner wallet relies on @austintgriffith to be deployed to e.g. xdai.io.
• As we'd like to ship to production as often as possible, having continuous integration would be nice.
• The LeapDAO team has already done this with their burner, so we could just copy what they're doing: chore: add travis CI config leapdao/plasma-burner-wallet#144
• Note that we might not want to deploy everything in master directly into production. As the code base is handling actual people's money, I'd propose we do as following:
  • Have a branch that deploys a burner-wallet to test.xdai.io with e.g. Rinkeby support (maybe that's master). Pro-tip for making Exchange.js work on Rinkeby: Uniswap has contracts deployed on Rinkeby
  • Have a branch that deploys to xdai.io (e.g. "production")

Deliverables

• Implement continuous deployment for the burner-wallet, a staging domain and a production domain
• Remove the now outdated scripts used for deployment

Notes

• This issue can only be resolved by someone having access to the hosting provider @austintgriffith uses. Make sure you talk to him first before starting this issue.
• Consider that Create well-defined git branch flow #208 and this issue might be related or dependent on each other.

Roles

bounty gardener: @TimDaub / 10%
bounty worker: name / 75%
bounty reviewer: name / 15%

[dmihal]

This is related to #208, regarding which branch is used for what.

My suggestion would be master is for production, and we have staging and develop as well with their own deployments as well.

I'd also suggest each PR gets an automatic "review app" deployed, assuming there's funding for that many instances.