Add future directions section to post
parent
d74eb1df58
commit
310a19bca5
|
@ -415,6 +415,9 @@ Now you should be able to use a command like this on a Docker-friendly host, and
|
|||
nix run .#deploy
|
||||
```
|
||||
|
||||
### Future Directions
|
||||
There is just a touch of boilerplate left in `flake.nix`, required to thread the correct nixpkgs context through (`callPackage`, passing `site` and `dockerImage` explicitly). We could easily package that up in a `flake-module.nix` and add it to the `imports` argument of `flake-parts.lib.mkFlake`. I'll probably try to make another blog post out of the process of packaging up the Nix glue, so keep your eyes peeled!
|
||||
|
||||
Thanks for reading!
|
||||
|
||||
## Acknowledgements
|
||||
|
|
|
@ -17,7 +17,7 @@
|
|||
systems = inputs.nixpkgs.lib.systems.flakeExposed;
|
||||
perSystem = { config, self', inputs', pkgs, system, ... }:
|
||||
let
|
||||
# TODO: move these to a flake-modules
|
||||
# TODO: move these to a flake-module
|
||||
inherit (pkgs.callPackage ./nix { }) container deploy fonts optimize-images themes;
|
||||
inherit (fonts) copyFonts linkFonts;
|
||||
inherit (themes {
|
||||
|
|
Loading…
Reference in New Issue