1442345 - Dev, Stage and Prod environments for Delivery Console

Status: RESOLVED FIXED

(Cloud Services :: Operations: Miscellaneous, task)

Description

[Peter Bengtsson [:peterbe]]

https://github.com/mozilla/delivery-console is a, under development, 100% client side application. It's a Single Page Application. We would like to host it with a CDN in front. 

We want to have three environments:
* Dev (auto-upgraded on commits to master)
* Stage (auto-upgrade on new tags)
* Prod (manually (cloudops) upgraded by tag)

We don't have a final domain name for it yet. If we need a name, call it "delivery-console". 

Our intention is to build the project in CI and use the build artifacts as the build to send to the server. The project is create-react-app based so the resulting builds is small directory looking something like this:

build/
  index.html
  static/
    css/
      main.hex1235.css
    js/
      main.hex1235.js
    someimage.svg

Since it's a Single Page App with its our in-browser routing, non-root URLs should serve up /index.html if it doesn't match a file. E.g. `curl .../normandy/about` should return `/index.html`. 

We don't have the CircleCI running yet but would appreciate guidance.

Comment 2

[Miles Crabill [:miles]]

We have three environments deployed with corresponding URLs:

https://delivery-console.dev.mozaws.net <- deployed off of latest commit on master
https://delivery-console.stage.mozaws.net <- deployed off of latest tag
https://delivery-console.prod.mozaws.net <- deployed manually by cloudops

A todo that has been discussed in backchannel is working out lambda@edge to handle rewriting SPA URLs so that they don't get passed erroneously to the S3 backend. As a stopgap solution, we have lambda@edge configured to route backend (s3) 4xxs to the root page (/) as /index.html (as mentioned above) returns a frontend 404. That work is to do on the dev side.

Comment 3

[Miles Crabill [:miles]]

I believe this is complete.