-
-
Notifications
You must be signed in to change notification settings - Fork 8
Configuration
For everything to work as desired, there are just a few simple steps to complete in the configuration. The configuration is set in the script.js file in the instance. The following items need to be configured
This configuration will specify which monitors to query for the status page. You can create them in the My Settings section of the site. You will need to generate API keys for each of your monitors and then copy them down. Scroll to the bottom, and use the Monitor-Specific Keys section to create these. Once you've created these for the desired sites, you will need to enter them into the configuration. The first section of the config look similar to:
uptimerobot: {
api_keys: [
'm779828614-2b8e76a1f638f179db6f01be',
'm779757287-11996787b4a4ddb79cae343b',
'm779757278-82acbbedc86d26ebbc129945',
'm779762016-33deea24d6a3e73e524d8ab0',
'm779870719-a710902a0c001a03244eac5e',
'm779870718-eada06ba00200d8ced148b37'
],
Here you will need to input your api keys to substitute. Be sure that for each entry it is enclosed in single quotes, and that multiple lines are followed by a comma at the end of the line. The last entry will not have a comma.
This configuration will provide the details of which GitHub repo will be monitored for issues that generate Incidents and Maintenance items on the page. This one is pretty straightforward. Find the following section in the config:
github: {
org: '1activegeek',
repo: 'status'
},
You will be substituting your Username in the org
heading. Under the repo, you will input the name of your repo that will be hosting the status page. This is where issues will be created to generate the incidents/maintenance items.
Please see the theme section for more details. This is not required to get started, but will allow further customization. Set the configuration by modifying the following line in the config. light
and dark
are the only options available currently.
},
theme: 'dark'
};