https://github.com/g3rhard/sysops-framework
SysOps Framework
https://github.com/g3rhard/sysops-framework
framework sysops vibe-coding
Last synced: 3 days ago
JSON representation
SysOps Framework
- Host: GitHub
- URL: https://github.com/g3rhard/sysops-framework
- Owner: g3rhard
- License: mit
- Created: 2025-09-04T12:36:53.000Z (10 months ago)
- Default Branch: main
- Last Pushed: 2026-07-01T23:53:39.000Z (12 days ago)
- Last Synced: 2026-07-02T01:23:12.298Z (12 days ago)
- Topics: framework, sysops, vibe-coding
- Language: Python
- Homepage: http://g3rhard.cc/sysops-framework/
- Size: 5.85 MB
- Stars: 1
- Watchers: 1
- Forks: 0
- Open Issues: 4
-
Metadata Files:
- Readme: README.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
Awesome Lists containing this project
README
# SysOps Framework
> An operations methodology for teams whose work doesn't fit sprint boundaries.
[](https://opensource.org/licenses/MIT)
[](https://github.com/g3rhard/sysops-framework)
[](https://github.com/g3rhard/sysops-framework/releases)
## What this is
The SysOps Framework replaces the single sprint cadence with three simultaneous cycles (daily, weekly, monthly) that match how operations work actually happens. It is a book, a methodology reference, and a set of downloadable templates - all in one repo.
## Start here on GitHub
If you are evaluating the project from the repository rather than the rendered site, use this order:
1. Read [Chapter 1 - The Challenge](content/docs/chapter-01-challenge.md) to check whether the problem matches your team.
2. Read [Chapter 3 - Framework Structure](content/docs/chapter-03-structure.md) to understand the daily / weekly / monthly operating model.
3. Use [Getting Started](content/docs/getting-started/_index.md) for a 30-day pilot.
4. Copy the templates from [`templates/`](templates/) only after you know which cycle or practice they support.
The repository is intentionally both a book and an operating kit: the chapters explain the model; the templates make it usable.
## Who it helps
Teams of highly skilled individual contributors sharing a team name but running separate projects, systems, and pagers. If Scrum/Kanban/SRE don't quite fit your ops mix, this is for you. See the **[full audience description](content/docs/_index.md)** for details.
## Browse locally
**Prerequisites**: Go, Node.js, and [Hugo extended edition](https://gohugo.io/installation/).
```bash
git clone https://github.com/g3rhard/sysops-framework
cd sysops-framework
# Fetch the Docsy theme and its dependencies
git submodule update --init --recursive
# Install npm packages (required by Docsy for PostCSS, etc.)
npm install
# Start the dev server
hugo server
```
Open http://localhost:1313/sysops-framework/.
## Read online
The fully rendered site is published at **[g3rhard.cc/sysops-framework](https://g3rhard.cc/sysops-framework/)**.
## Download
PDF and EPUB versions are built automatically from the latest tagged release:
- [Releases page](https://github.com/g3rhard/sysops-framework/releases)
- All templates are in the [`templates/`](templates/) directory - PIR, change control, on-call policy, SLA, and more
## What's auto-generated
| Artifact | Source | Trigger |
| ----------------- | ----------------------------------- | ---------------------------------- |
| GitHub Pages site | `content/` + Hugo | Push to `main` |
| PDF / EPUB | `content/` → Pandoc + lualatex | Tagged release (`v*`) |
## Docs architecture and contribution model
- `content/docs/` contains the book and rendered documentation.
- `templates/` contains reusable operational artifacts.
- `scripts/diagrams/` generates visual assets used by the site.
- Keep vendor/tool recommendations dated and easy to refresh; durable concepts belong in chapters, fast-aging tool choices belong in tables or notes.
When contributing, prefer small documentation PRs that improve one reader journey at a time: primer, adoption, reference, or templates.
## Quick links
- [Chapter 1 - The Challenge](content/docs/chapter-01-challenge.md)
- [Chapter 6 - 12 Management Practices](content/docs/chapter-06-practices.md)
- [Implementation roadmap](content/docs/chapter-05-implementation.md)
- [Glossary](content/docs/glossary.md)
- [Appendices / templates](content/docs/chapter-13-appendices.md)
## License
MIT - see [LICENSE](LICENSE).