NixOS-like services for Nix flakes
Go to file
2023-12-19 09:03:09 -05:00
.github/workflows add github action workflow for https://github.com/flakestry/flakestry.dev 2023-10-27 15:38:50 +05:30
dev docs: flakular rename 2023-11-17 15:08:15 -05:00
doc doc: edit; add wip status 2023-07-21 14:08:44 -04:00
example process-compose: 0.60.0 -> 0.65.1 (#58) 2023-10-07 23:56:28 +05:30
nix Namespaces (#57) 2023-10-04 22:50:59 +05:30
test process-compose: 0.60.0 -> 0.65.1 (#58) 2023-10-07 23:56:28 +05:30
.envrc Revert "dev flake: check example and tests" 2023-07-10 19:36:14 -04:00
.gitignore Add dev flake 2023-06-21 16:07:19 -04:00
flake.nix nixci: Remove unused config 2023-10-19 14:19:07 -04:00
justfile Process as test (VM -> Native test) (#38) 2023-08-23 22:47:20 +05:30
LICENSE Initial commit 2023-06-19 17:44:27 -04:00
README.md readme: Use new doc links 2023-12-19 09:03:09 -05:00

services-flake

Note

🚧 Work in Progress

NixOS-like services for Nix flakes, as a process-compose-flake module (based on flake-parts).

Getting Started

$ nix flake new --template github:juspay/services-flake ./my-project
$ cd my-project
$ nix run

Or see ./test/flake.nix

Services available

  • Apache Kafka
  • Elasticsearch
  • MySQL
  • PostgreSQL
  • Redis
  • Redis Cluster
  • Zookeeper
  • ...

A note on process working directory

The dataDir of these services tend to take relative paths, which are usually relative to the project root. As such, when you run these services using nix run, their data files are created relative to whichever directory you are in. If you want these data files to always reside relative to the project directory, instead of using nix run consider wrapping the process-compose packages in script, via either mission-control module or a justfile. The example uses the latter.

Discussions

To discuss the project, please join our Zulip.

Contributing

Credits

Thanks to the devenv project on which much of our services implementation is based on.

FAQ

Why not re-use devenv service modules?

This is currently not possible (nor prioritized by the devenv project), which is why we must create our own services. See https://github.com/cachix/devenv/issues/75