Skip to content

Add Nix deployment support - #260

Open
benthecarman wants to merge 1 commit into
lightningdevkit:mainfrom
benthecarman:nix-ldk-deploy
Open

Add Nix deployment support#260
benthecarman wants to merge 1 commit into
lightningdevkit:mainfrom
benthecarman:nix-ldk-deploy

Conversation

@benthecarman

Copy link
Copy Markdown
Collaborator

ix-bitcoin is archived and no longer receives security fixes. Provide
a maintained upstream path for reproducible builds and declarative
NixOS deployment.

The flake pins Nixpkgs and exports a package and NixOS module. The
package builds the server and CLI, takes its version from Cargo, and
installs shell completions. The module creates a service, user,
configuration, state directory, and optional firewall ports for each
named instance. The documentation covers local builds, deployment,
secrets, and multiple instances.

nix-bitcoin is archived and no longer receives security fixes. Provide
a maintained upstream path for reproducible builds and declarative
NixOS deployment.

The flake pins Nixpkgs and exports a package and NixOS module. The
package builds the server and CLI, takes its version from Cargo, and
installs shell completions. The module creates a service, user,
configuration, state directory, and optional firewall ports for each
named instance. The documentation covers local builds, deployment,
secrets, and multiple instances.

Generated with OpenAI Codex.
@ldk-reviews-bot

ldk-reviews-bot commented Aug 20, 2026

Copy link
Copy Markdown

👋 Thanks for assigning @tnull as a reviewer!
I'll wait for their review and will help manage the review process.
Once they submit their review, I'll check if a second reviewer would be helpful.

@benthecarman
benthecarman requested review from tnull and removed request for wpaulino August 20, 2026 06:46

@tnull tnull left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So far we took the stance that we shouldn't add distro or build system specific code to the repo (mod. docker files, maybe) (see #68 (review) for instance). Adding such files will add to the maintenance burden so we should be careful what we commit to supporting.

Do you think it makes sense to officially support this? Or should it just be a separate repo you maintain?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants