openva/va-decoded

Set up a staging server and deployment process

waldoj opened this issue · 7 comments

  • set up beta.vacode.org on the web server
  • establish automated deployments
  • figure out how to store secrets (maybe just put config.inc.php elsewhere on the web server?)
  • set up a Travis-based deploy process
  • make statedecoded/statedecoded a submodule
  • deploy code to EC2 with CodeDeploy
  • run statedecoded test-env and ensure that it runs cleanly
  • re-run the parser when the XSLT, XML, or import class is modified

(Perhaps Travis CI isn't the best way to do this.)

Travis CI was not. Setting up a GitHub webhook and a script on the server was the way to go.

I put the config file in another directory on the server, and copy it over with the commit script. Works great.

I'll leave this open until I have the site actually running, instead of available to be configured.

@krues8dr: Changes to this repo should now be deployed to beta.vacode.org!

(Like, automatically. :)