> If you want to create docker image of your own app, you probably would use [...] Nixery can be pointed at your own package set, in fact I do this for deploym

> If you want to create docker image of your own app, you probably would use [...] Nixery can be pointed at your own package set, in fact I do this for deployments of my personal services[0]. This doesn't interfere with any of the local Nix functionality. I find it makes for a pleasing CI loop, where CI builds populate my Nix cache[1] and deployment manifests just need to be updated with the most recent git commit hash[2]. (I'm the author of Nixery) [0]: https://git.tazj.in/tree/ops/infra/kubernetes/nixery https://git.tazj.in/tree/ops/infra/kubernetes/nixery [1]: https://git.tazj.in/tree/ops/sync-gcsr/manifest.yaml#n17 https://git.tazj.in/tree/ops/sync-gcsr/manifest.yaml#n17 [2]: https://git.tazj.in/tree/ops/infra/kubernetes/tazblog/config.yaml#n20 https://git.tazj.in/tree/ops/infra/kubernetes/tazblog/config...