Name: status-site
Owner: CyVerse
Description: Site providing status of CyVerse services
Created: 2016-02-08 18:02:22.0
Updated: 2018-05-22 17:29:45.0
Pushed: 2018-05-22 17:29:44.0
Homepage: http://status.cyverse.org/
Size: 4281
Language: JavaScript
GitHub Committers
User | Most Recent Commit | # Commits |
---|
Other Committers
User | Most Recent Commit | # Commits |
---|
This is currently running here: http://status.cyverse.org/
The intention of this web-app is to determine which services are currently operational. One can subscribe to downtime notifications for each respective service. This App is currently hosted via Heroku, as it is completely outside of our infrastructure and can accurately determine operability of our services.
For instructions on how to set the status.io
status for each product, see instructions here.
First create a fork of this repo (fork button in upper right corner).
Clone your fork.
clone git@github.com:<username>/status-site.git
Navigate into the project and install dependencies.
tatus-site;
i
Start web app.
run start
This App is configured to work directly with Heroku and thus requires specific package definitions and dependencies to “deploy” with Heroku. One of these dependencies is Sails.
Download and install the Heroku Toolbelt: https://toolbelt.heroku.com/
Configure DNS via AWS Route 53 for the Heroku App name: https://console.aws.amazon.com/route53
Clone the status-site
repository (this repo): https://github.com/cyverse/status-site
Use Heroku Toolbelt to add domain and host to the App: https://devcenter.heroku.com/articles/route-53
ku login
ku domains:add cyverse.org --app cyverse-status
ku domains:add status.cyverse.org --app cyverse-status
Perform steps 1-3 in the Add instructions.
Remove associated domain with the hosted App: https://devcenter.heroku.com/articles/custom-domains#remove-a-custom-domain
ku domains:remove cyverse.org --app cyverse-the-movie
ku domains:remove status.cyverse.org --app cyverse-the-movie
Then re-add the App's new DNS CNAME domain and hostname as shown in step 4. of adding DNS.
Give DNS a full 24 hours (perhaps less) to propagate to the outside world. The changes may show up faster if your host has AWS Route 53's domain in your DNS configuration.
Done!