You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 28, 2019. It is now read-only.
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.
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?
The text was updated successfully, but these errors were encountered:
mine is gonna be pretty limited, because I discovered a bit of a problem..... Turns out the "you bewt" hard disk in my big notebook can't handle the disk IO caused by a USB 3 hard drive... So when we're doing up these vms I am gonna have an unusable environment while it runs
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
The text was updated successfully, but these errors were encountered: