Add deployment listing and sunset workflows

[findolor]

Depends on

• Deploy named local DB sync instances #7

Motivation

Named deployments need basic operations after they are created: reviewers and operators should be able to see what is running, and old deployment instances should be easy to sunset after the web application has moved to a new manifest.

Solution

• add a manual List Deployments workflow that reports deployment ID, timer status, service status, settings URL, service start time, next timer run, and work directory size
• add a manual Sunset Deployment workflow that stops and disables one named deployment
• keep deployment env, binary, and work state by default for rollback
• add an explicit delete_state option for removing a deployment's host-side state
• document deployment IDs, side-by-side operation, listing, and sunset behavior in README.md

Checks

By submitting this for review, I am confirming I have done the following:

• made this PR as small as possible
• unit-tested any new functionality
• linked any relevant issues or PRs
• included screenshots (if this involves a front-end change)

Validated locally with:

• YAML parse for .github/workflows/deploy.yaml, .github/workflows/list-deployments.yaml, and .github/workflows/sunset-deployment.yaml
• bash -n nixos/local-db-remote-run.sh
• nix eval '.#nixosConfigurations.local-db-remote.config.systemd.timers."local-db-sync@".timerConfig.Unit'

[coderabbitai]

Warning

Review limit reached

@findolor, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 17 minutes. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: b9df114e-539e-4bf5-9300-4e4148b91233

📥 Commits

Reviewing files that changed from the base of the PR and between 7c057e8 and f83655b.

📒 Files selected for processing (3)

• .github/workflows/list-deployments.yaml
• .github/workflows/sunset-deployment.yaml
• README.md

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feature/deployment-id-ops

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[findolor]

• Bump raindex for derived vault deltas deployment #10
• Bump raindex for derived trades local DB #9
• Add deployment listing and sunset workflows #8 👈 (View in Graphite)
• Deploy named local DB sync instances #7
• Add deployment-id sync units #6
• Update deployment SSH key ownership and allow branch-based workflow testing #5
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[findolor]

Merge activity

• May 26, 3:00 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 26, 3:06 PM UTC: Graphite rebased this pull request as part of a merge.
• May 26, 3:06 PM UTC: @findolor merged this pull request with Graphite.