Separate Litestream into its own systemd service#95
Merged
Conversation
Litestream's -exec wrapper prevents the Go binary from receiving socket file descriptors, blocking future socket activation for zero-downtime deploys. Running Litestream as an independent service also gives cleaner restart semantics — app deploys no longer restart replication unnecessarily. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
swalkinshaw
approved these changes
Apr 4, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
litestream -execwrapper into a standalonelitestream.servicewppackages.service, withRequires=andAfter=ordering on LitestreamWhy
The
litestream -execwrapper prevents the Go binary from receivingsocket file descriptors, which blocks socket activation for zero-downtime
deploys (#67). Separating the services also means app deploys no longer
bounce Litestream replication unnecessarily.
Ref: #67 (comment)
Test plan
provisionand verifylitestream.serviceis installed, enabled, and activewppackages.servicestarts after Litestream and serves trafficdeploy(app restart should not restart Litestream)journalctl -u litestreamfor healthy replication after provision🤖 Generated with Claude Code