Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nix Flake all the things or use alongside Docker? #312

Open
Kodylow opened this issue Mar 14, 2023 · 2 comments
Open

Nix Flake all the things or use alongside Docker? #312

Kodylow opened this issue Mar 14, 2023 · 2 comments

Comments

@Kodylow
Copy link

Kodylow commented Mar 14, 2023

Made a first pass at building the flake.nix today and got it working with the rust build and environment variables.

Should the flake.nix run the entire project as a standalone, so build and use its own postgres and redis through nix without docker, or do you want it to run alongside docker? Can do either one.

@bodymindarts
Copy link
Member

Good question - though I have nix I haven't used flakes yet. What is more common? I guess it would be good to support both for ppl not on the nix train yet.
I'm thinking probably not using docker at all is more idiomatic for a flakes.nix setup isn't it? Perhaps we start with that to experiment but we can change it if needed.

@Kodylow
Copy link
Author

Kodylow commented Mar 14, 2023

More common to do everything through nix but I see that you're using docker for the rest of the stack so wanted to check. I think making it as a standalone could be helpful for starting to decouple from the galoy backend , could do work in nix shell and update the nix environment variables as a sandbox to avoid breaking your regular ci/cd and https://github.com/fort-nix/nix-bitcoin is great for testing integrations against other bitcoin and lightning node implementations once stablesats gets to that point.

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

No branches or pull requests

2 participants