A statuspage generator that lets you host your statuspage for free on Github.
Project description
# Statuspage
[![Updates](https://pyup.io/repos/github/jayfk/statuspage/shield.svg)](https://pyup.io/repos/github/jayfk/statuspage/)
[![Python 3](https://pyup.io/repos/github/jayfk/statuspage/python-3-shield.svg)](https://pyup.io/repos/github/jayfk/statuspage/)
[![Build Status](https://travis-ci.org/jayfk/statuspage.svg?branch=master)](https://travis-ci.org/jayfk/statuspage)
[![codecov.io](https://codecov.io/github/jayfk/statuspage/coverage.svg?branch=master)](https://codecov.io/github/jayfk/statuspage?branch=master)
A statuspage generator that lets you host your statuspage for free on GitHub. Uses
issues to display incidents and labels for severity.
## Demo
![DEMO](https://github.com/jayfk/statuspage/blob/master/demo.gif)
See a real status page generated by this at [status.pyup.io](http://status.pyup.io/) or a [demo site](https://jayfk.github.io/statuspage-demo/)
## Quickstart
Install statuspage with pip:
pip install statuspage
*There are also binaries for macOS and Linux available, see [installation](docs/installation.md) for more.
Now, create an GitHub API token:
- Go to your [Personal Access tokens](https://github.com/settings/tokens) page.
- Click on `Generate new token`.
- Make sure to check the `public_repo` and `write:repo_hook` scope.
- Copy the token somewhere safe, you won't be able to see it again once you leave the page.
To create a new status page, run:
statuspage create --token=<yourtoken>
You'll be prompted for the name and the systems you want to show a status for.
Name: mystatuspage
Systems, eg (Website,API): Website, CDN, API
*Please note: name, bla bla bla*
The command takes a couple of seconds to run. Once ready, it will output links to the issue tracker and your new status page.
Create new issues at https://github.com/<login>/mystatuspage/issues
Visit your new status page at https://<login>.github.com/mystatuspage/
Next, you will be asked if you want to automate the update process, so that you don't have to run
the `statuspage update` command whenever you change anything on your repo.
Set up automation? [y/N]: y
If you want use the service, choose `y` and grab a key at the [shop](https://www.statuspage-backend.com).
If you don't want to use the service, choose `n`. The generator will then print the `statuspage update`
command filled with all the details you need to update your page.
## Create an issue
To create a new issue, go to your newly created repo and click on `New Issue`.
- Click on the cog icon next to labels on the right.
- Choose the affected systems (black labels)
- Choose a severity label (major outage, degraded performance, investigating)
- Fill in the title, leave a comment and click on `Submit new issue`.
![Add New Issue](docs/new_issue.png)
Now, update your status page. Go back to your commandline and type:
statuspage update --token=<yourtoken>
Name: mystatuspage
If you change the issue (eg. when you add a new label, create a comment or close the issue), you'll
need to run `statuspage update` again.
## Customizing
See [customizing](docs/customizing.md)
## Options
See [options](docs/options.md)
# Change Log
All enhancements and patches to statuspage will be documented in this file.
This project adheres to [Semantic Versioning](http://semver.org/).
## 0.6.0 [2016-07-26]
- Added an option to automate the update process.
- Switch to PyGithub as pygithub-redux is no longer needed
- Added an option to create private repositories
- Beefed up the docs
## 0.5.1 [2016-07-26]
- Updated dependencies: tqdm and pygithub-redux
## 0.5.0 [2016-07-26]
- Systems and Panels are now ordered to make sure that no commit is issued when nothing changes (#12)
- Refactored the code to make it easier to read
## 0.4.1 [2016-07-25]
- Fixed a bug on python 3 where the hash function wasn't working.
## 0.4.0 [2016-07-25]
- Only commit if content differs (@Jcpetrucci)
## 0.3.3 [2016-07-13]
- issued new pypi release
## 0.3.2 [2016-07-13]
- fixed packaging problems by using a module
- minified and merged style.css with milligram.min.css
## 0.3.1 [2016-07-12]
- fixed packaging problems
## 0.3 [2016-07-12]
- statuspage is now available on PyPi
## 0.2 [2016-03-08]
- Added support for GitHub organizations
- Makes sure that non-collaborator issues/comments are not displayed
## 0.1 [2016-03-07]
- Initial release
[![Updates](https://pyup.io/repos/github/jayfk/statuspage/shield.svg)](https://pyup.io/repos/github/jayfk/statuspage/)
[![Python 3](https://pyup.io/repos/github/jayfk/statuspage/python-3-shield.svg)](https://pyup.io/repos/github/jayfk/statuspage/)
[![Build Status](https://travis-ci.org/jayfk/statuspage.svg?branch=master)](https://travis-ci.org/jayfk/statuspage)
[![codecov.io](https://codecov.io/github/jayfk/statuspage/coverage.svg?branch=master)](https://codecov.io/github/jayfk/statuspage?branch=master)
A statuspage generator that lets you host your statuspage for free on GitHub. Uses
issues to display incidents and labels for severity.
## Demo
![DEMO](https://github.com/jayfk/statuspage/blob/master/demo.gif)
See a real status page generated by this at [status.pyup.io](http://status.pyup.io/) or a [demo site](https://jayfk.github.io/statuspage-demo/)
## Quickstart
Install statuspage with pip:
pip install statuspage
*There are also binaries for macOS and Linux available, see [installation](docs/installation.md) for more.
Now, create an GitHub API token:
- Go to your [Personal Access tokens](https://github.com/settings/tokens) page.
- Click on `Generate new token`.
- Make sure to check the `public_repo` and `write:repo_hook` scope.
- Copy the token somewhere safe, you won't be able to see it again once you leave the page.
To create a new status page, run:
statuspage create --token=<yourtoken>
You'll be prompted for the name and the systems you want to show a status for.
Name: mystatuspage
Systems, eg (Website,API): Website, CDN, API
*Please note: name, bla bla bla*
The command takes a couple of seconds to run. Once ready, it will output links to the issue tracker and your new status page.
Create new issues at https://github.com/<login>/mystatuspage/issues
Visit your new status page at https://<login>.github.com/mystatuspage/
Next, you will be asked if you want to automate the update process, so that you don't have to run
the `statuspage update` command whenever you change anything on your repo.
Set up automation? [y/N]: y
If you want use the service, choose `y` and grab a key at the [shop](https://www.statuspage-backend.com).
If you don't want to use the service, choose `n`. The generator will then print the `statuspage update`
command filled with all the details you need to update your page.
## Create an issue
To create a new issue, go to your newly created repo and click on `New Issue`.
- Click on the cog icon next to labels on the right.
- Choose the affected systems (black labels)
- Choose a severity label (major outage, degraded performance, investigating)
- Fill in the title, leave a comment and click on `Submit new issue`.
![Add New Issue](docs/new_issue.png)
Now, update your status page. Go back to your commandline and type:
statuspage update --token=<yourtoken>
Name: mystatuspage
If you change the issue (eg. when you add a new label, create a comment or close the issue), you'll
need to run `statuspage update` again.
## Customizing
See [customizing](docs/customizing.md)
## Options
See [options](docs/options.md)
# Change Log
All enhancements and patches to statuspage will be documented in this file.
This project adheres to [Semantic Versioning](http://semver.org/).
## 0.6.0 [2016-07-26]
- Added an option to automate the update process.
- Switch to PyGithub as pygithub-redux is no longer needed
- Added an option to create private repositories
- Beefed up the docs
## 0.5.1 [2016-07-26]
- Updated dependencies: tqdm and pygithub-redux
## 0.5.0 [2016-07-26]
- Systems and Panels are now ordered to make sure that no commit is issued when nothing changes (#12)
- Refactored the code to make it easier to read
## 0.4.1 [2016-07-25]
- Fixed a bug on python 3 where the hash function wasn't working.
## 0.4.0 [2016-07-25]
- Only commit if content differs (@Jcpetrucci)
## 0.3.3 [2016-07-13]
- issued new pypi release
## 0.3.2 [2016-07-13]
- fixed packaging problems by using a module
- minified and merged style.css with milligram.min.css
## 0.3.1 [2016-07-12]
- fixed packaging problems
## 0.3 [2016-07-12]
- statuspage is now available on PyPi
## 0.2 [2016-03-08]
- Added support for GitHub organizations
- Makes sure that non-collaborator issues/comments are not displayed
## 0.1 [2016-03-07]
- Initial release
Project details
Release history Release notifications | RSS feed
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
statuspage-0.6.0.tar.gz
(16.5 kB
view hashes)
Built Distribution
statuspage-0.6.0-py2-none-any.whl
(27.2 kB
view hashes)
Close
Hashes for statuspage-0.6.0-py2-none-any.whl
Algorithm | Hash digest | |
---|---|---|
SHA256 | 22fa50f1f7560f640e487a0185dd6de440cc449bd013e509d273cf034eadfd66 |
|
MD5 | 4558557562829c36c84982d4b218460a |
|
BLAKE2b-256 | b1277cf887d1b08f5ab3c5a8baa4eecd600d17118aef4b8eecb9bc1f220e4301 |