NixOS-like services for Nix flakes
Go to file
shivaraj-bh f2e16df269 init
2023-08-30 10:24:38 -04:00
.github/workflows init 2023-08-30 10:24:38 -04:00
dev dev: Switch from mission-control to just 2023-07-20 07:59:17 -04:00
doc doc: edit; add wip status 2023-07-21 14:08:44 -04:00
example Process as test (VM -> Native test) (#38) 2023-08-23 22:47:20 +05:30
nix Kafka and Zookeeper services (#42) 2023-08-29 17:04:04 +05:30
test Kafka and Zookeeper services (#42) 2023-08-29 17:04:04 +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 Add nixci config to flake (#19) 2023-07-10 21:25:49 -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 Add elasticsearch service (#37) 2023-08-23 23:07:18 +05:30

services-flake

Note

🚧 Work in Progress

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

Getting Started

TODO

(But see ./test/flake.nix)

Services available

  • PostgreSQL
  • MySQL
  • Redis
  • Redis Cluster
  • Elasticsearch
  • ...

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.

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