This repository was archived by the owner on Nov 28, 2019. It is now read-only.

Description
I've been looking around at some options for our fallback server... Might be doubling up on what @mbainrot and @kaleyh have been doing, but here are my ideas.
- gitlab as fallback from github - should have cronjob running git to pull down latest from github regularly so if we have to fallback it is up to date. Maybe modify this https://github.com/gitlabhq/gitlab-recipes/blob/master/import/github/import_all.rb if it can keep issues & milestones in sync?
- some sort of CI to fall back from Travis- maybe just our tests being run from a githook. Have looked at Jenkins, but might be too much to get that going. GitLab has CI module (https://about.gitlab.com/gitlab-ci/) but may have licencing/setup issues.
- dashing install to generate dashboard from local data if internet fails
- apache virtual hosts configured for whatever we are building as well - dev / prod - dev updated when CI/testing passes. Maybe manual update for prod?