You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Marius Pana 5f961d223d fixed travis-ci build badge 3 years ago
_site update cf last stand-up 3 years ago
docs update cf last stand-up 3 years ago
theme minor edits to main page 3 years ago
.DS_Store travis.yml, gh-deploy 3 years ago
.gitignore do not add .git to repo 3 years ago
.travis.yml we do not need awscli 3 years ago
CNAME adding CNAME as the custom domain name dissapears after ever 3 years ago
LICENSE travis.yml, gh-deploy 3 years ago
README.md fixed travis-ci build badge 3 years ago
mkdocs.yml updating to spearhead specifics 3 years ago
screenshot.png travis.yml, gh-deploy 3 years ago

README.md

Spearhead Systems Issue Response Documentation Build Status

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.

You can view the documentation directly in this repository, or rendered as a website at https://response.spearhead.systems.

Spearhead Systems Issue Response Documentation

Development

We use MkDocs to create a static site from this repository. For local development,

  1. Install MkDocs. pip install mkdocs
  2. Install the MkDocs Material theme. pip install mkdocs-material==0.2.4
  3. To test locally, run mkdocs serve from the project directory.

Deploying

  1. Run mkdocs build --clean to produce the static site for upload.
  2. Upload the 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
    

License

Apache 2 (See LICENSE file)

Contributing

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,

  1. Fork it ( https://github.com/PagerDuty/incident-response-docs/fork )
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create a new Pull Request.