fieldju/dinghy — explained in plain English
Analysis updated 2026-07-17 · repo last pushed 2024-02-13
Define Spinnaker deployment pipelines as version-controlled YAML or JSON files instead of clicking through a UI.
Build reusable stage and task templates that multiple pipelines can share and inherit updates from.
Automatically rebuild Spinnaker pipelines when a linked GitHub repo receives a push via webhook.
Let a team code-review deployment pipeline changes the same way they review application code.
| fieldju/dinghy | 0verflowme/alarm-clock | 0xhassaan/nn-from-scratch | |
|---|---|---|---|
| Stars | — | — | 0 |
| Language | — | CSS | Python |
| Last pushed | 2024-02-13 | 2022-10-03 | — |
| Maintenance | Dormant | Dormant | — |
| Setup difficulty | hard | easy | moderate |
| Complexity | 4/5 | 2/5 | 4/5 |
| Audience | ops devops | vibe coder | developer |
Figures from each repo's GitHub metadata at analysis time.
Needs a running Spinnaker instance plus supporting services like Redis and Front50.
Dinghy lets you write and manage Spinnaker pipelines the same way you'd manage code, by storing them in GitHub and updating them through pull requests instead of clicking through a web interface. Spinnaker is a tool for automating software deployments. Normally, you'd build deployment pipelines by hand using Spinnaker's UI, which gets tedious and hard to review. Dinghy changes this by letting you define pipelines as text files in a Git repository. You create reusable pieces (called stage and task templates) that you can mix and match to build complete pipelines. When you push changes to GitHub, Dinghy automatically detects the update through webhooks and rebuilds the pipeline in Spinnaker. If you update a template, Dinghy knows which pipelines depend on it and refreshes those too. The workflow looks like this: you write a pipeline definition file (like a blueprint) that references stage templates. These templates are stored in a GitHub repository and contain placeholder values you can customize. When the template or pipeline definition changes, GitHub sends a notification to Dinghy, which parses the files, fills in any variables, and syncs the result back to Spinnaker. This keeps everything in version control, makes it easy to review changes, and lets your team collaborate on deployment logic the same way they do on code. Teams that manage multiple deployment pipelines, especially at companies running several applications or microservices, would find this useful. Instead of each developer learning Spinnaker's UI, they can write YAML or JSON files, commit them, get code review, and let Dinghy handle the rest. It's particularly valuable if you already use GitHub for source control and want a consistent workflow across your infrastructure. The project is built in Go and needs a running instance of Spinnaker (along with specific services like Redis and Front50) to work. The README also mentions that Dinghy integrates with the Armory CLI tool if you want to validate pipelines locally before pushing them up.
Dinghy lets teams manage Spinnaker deployment pipelines as text files in GitHub, syncing changes to Spinnaker automatically instead of editing pipelines by hand in a web UI.
Dormant — no commits in 2+ years (last push 2024-02-13).
License terms are not stated in the explanation.
Setup difficulty is rated hard, with roughly 1h+ to a first successful run.
Mainly ops devops.
This repo across BitVibe Labs
Verify against the repo before relying on details.