https://github.com/PagerDuty/goingoncall-docs

Repository for the Best Practices for On Call Teams Ops Guide
https://github.com/PagerDuty/goingoncall-docs

team-community

Last synced: 5 days ago
JSON representation

Repository for the Best Practices for On Call Teams Ops Guide

• Host: GitHub
• URL: https://github.com/PagerDuty/goingoncall-docs
• Owner: PagerDuty
• License: apache-2.0
• Created: 2021-01-11T17:01:23.000Z (almost 4 years ago)
• Default Branch: main
• Last Pushed: 2022-08-17T22:42:44.000Z (about 2 years ago)
• Last Synced: 2024-05-08T12:32:14.272Z (6 months ago)
• Topics: team-community
• Language: Dockerfile
• Homepage: https://goingoncall.pagerduty.com
• Size: 3.57 MB
• Stars: 7
• Watchers: 9
• Forks: 3
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

• awesome-cloud-security - PagerDuty Going OnCall Docs

README

        
# PagerDuty Best Practices for On-Call Teams Guide

[![Netlify Status](https://api.netlify.com/api/v1/badges/b7c1acb1-b332-461c-a9bf-67920caa38de/deploy-status)](https://app.netlify.com/sites/oncall-practices-d415fc/deploys)

This guide is a collection of resources from PagerDuty and others that is intended to help teams new to being on-call navigate the ins and outs of response.

You can view the documentation directly in this repository, or rendered as a website at https://goingoncall.pagerduty.com.

[![PagerDuty Best Practices for On Call Teams](screenshot.png)](https://goingoncall.pagerduty.com/)

## Development

We use [MkDocs](http://www.mkdocs.org/) to create a static site from this repository.

### Native

For local development on your native device,

1. Install [MkDocs](http://www.mkdocs.org/#installation). `pip install mkdocs`

1. Install [MkDocs PyMdown Extensions](https://squidfunk.github.io/mkdocs-material/extensions/pymdown/). `pip install pymdown-extensions`

1. Install [Pygments](https://pygments.org/) if you want syntax highlighting for any code examples. `pip install pygments`

1. Install the [PagerDuty MkDocs Theme](https://github.com/pagerduty/mkdocs-theme-pagerduty).

    1. `git clone https://github.com/pagerduty/mkdocs-theme-pagerduty`

    1. `cd mkdocs-theme-pagerduty & python3 setup.py install`

1. To test locally, run `mkdocs serve` from the project directory.

1. You can now view the website in your browser at `http://127.0.0.1:8000`. The site will automatically update as you edit the code.

### Docker

For local development using Docker,

1. Build the docker image and load it for immediate use. `docker build --load -t mkdocs .`

1. Run the container and pass through your current working directory. `docker run -v $(pwd):/docs -p 127.0.0.1:8000:8000 mkdocs`

1. You can now view the website in your browser at `http://127.0.0.1:8000`. The site will automatically update as you edit the code.

_Note: If you're using an Apple Silicon device, add `--platform linux/arm64/v8` to the `docker build` command to get a native Apple Silicon image. That will work faster than translating an arm64 image._

## Deploying

1. Run `mkdocs build --clean` to produce the static site for upload.

1. 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](http://www.apache.org/licenses/LICENSE-2.0) (See [LICENSE](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/goingoncall-docs/fork )

1. Create your feature branch (`git checkout -b my-new-feature`)

1. Commit your changes (`git commit -am 'Add some feature'`)

1. Push to the branch (`git push origin my-new-feature`)

1. Create a new Pull Request.