whatisgithub

What is dinghy?

fieldju/dinghy — explained in plain English

Analysis updated 2026-07-17 · repo last pushed 2024-02-13

Audience · ops devopsComplexity · 4/5DormantSetup · hard

In one sentence

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.

Mindmap

mindmap
  root((repo))
    What it does
      Pipelines as code
      Syncs via webhooks
    Tech Stack
      Go
      Spinnaker
      GitHub webhooks
    Use Cases
      Version control pipelines
      Reusable templates
    Audience
      DevOps engineers
      Platform teams
    Requires
      Redis
      Front50

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

What do people build with it?

USE CASE 1

Define Spinnaker deployment pipelines as version-controlled YAML or JSON files instead of clicking through a UI.

USE CASE 2

Build reusable stage and task templates that multiple pipelines can share and inherit updates from.

USE CASE 3

Automatically rebuild Spinnaker pipelines when a linked GitHub repo receives a push via webhook.

USE CASE 4

Let a team code-review deployment pipeline changes the same way they review application code.

What is it built with?

GoSpinnakerRedisFront50GitHub

How does it compare?

fieldju/dinghy0verflowme/alarm-clock0xhassaan/nn-from-scratch
Stars0
LanguageCSSPython
Last pushed2024-02-132022-10-03
MaintenanceDormantDormant
Setup difficultyhardeasymoderate
Complexity4/52/54/5
Audienceops devopsvibe coderdeveloper

Figures from each repo's GitHub metadata at analysis time.

How do you get it running?

Difficulty · hard Time to first run · 1h+

Needs a running Spinnaker instance plus supporting services like Redis and Front50.

License terms are not stated in the explanation.

So what is it?

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.

Copy-paste prompts

Prompt 1
Write a Dinghy pipeline definition file that references a reusable stage template.
Prompt 2
Explain how Dinghy detects and syncs changes from a GitHub webhook into Spinnaker.
Prompt 3
Show me how to structure a Dinghy stage template so multiple pipelines can reuse it.
Prompt 4
What do I need running (Redis, Front50) before Dinghy can sync pipelines to Spinnaker?

Frequently asked questions

What is dinghy?

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.

Is dinghy actively maintained?

Dormant — no commits in 2+ years (last push 2024-02-13).

What license does dinghy use?

License terms are not stated in the explanation.

How hard is dinghy to set up?

Setup difficulty is rated hard, with roughly 1h+ to a first successful run.

Who is dinghy for?

Mainly ops devops.

Open on GitHub → Ask about another repo

This repo across BitVibe Labs

Verify against the repo before relying on details.