|Marius Pana 5f961d223d fixed travis-ci build badge||3 years ago|
|_site||3 years ago|
|docs||3 years ago|
|theme||3 years ago|
|.DS_Store||3 years ago|
|.gitignore||3 years ago|
|.travis.yml||3 years ago|
|CNAME||3 years ago|
|LICENSE||3 years ago|
|README.md||3 years ago|
|mkdocs.yml||3 years ago|
|screenshot.png||3 years ago|
This is a public version of the Issue Response process used at Spearhead Ststems. It is based on the PagerDuty Incident Response process, modified to fit our specific requirements. It is used to prepare new employees for on-call responsibilities, and provides information not only on preparing for an issue (incident or service request), but also what to do during and after. See the about page for more information on what this documentation is and why it exists.
We use MkDocs to create a static site from this repository. For local development,
pip install mkdocs
pip install mkdocs-material==0.2.4
mkdocs servefrom the project directory.
mkdocs build --cleanto produce the static site for upload.
site directory to S3 (or wherever you would like it to be hosted).
aws s3 sync ./site/ s3://[BUCKET_NAME] \ --acl public-read \ --exclude "*.py*" \ --delete
Thank you for considering contributing! If you have any questions, just ask - or submit your issue or pull request anyway. The worst that can happen is we’ll politely ask you to change something. We appreciate all friendly contributions.
Here is our preferred process for submitting a pull request,
git checkout -b my-new-feature)
git commit -am 'Add some feature')
git push origin my-new-feature)