I have a deployment server which also runs a nix binary cache (attic). The deployment server is rather slow and I have a (local) CI machine which regularly pushes updates to the binary cache. For me it doesn't make sense to build the config (again) by bento, even if it just fetches all the build artifacts from attic.
So I added an option to not build the config by bento. I suppose it could be beneficial for the following usecases:
slow or underpowered deployment server
wrong architecture of the deployment server (e.g. Raspberry Pi)
limited disk space of the deployment server
convoluted build environments with CI server (or any server which builds the config separately)
fixes #5
I have a deployment server which also runs a nix binary cache (attic). The deployment server is rather slow and I have a (local) CI machine which regularly pushes updates to the binary cache. For me it doesn't make sense to build the config (again) by bento, even if it just fetches all the build artifacts from attic.
So I added an option to not build the config by bento. I suppose it could be beneficial for the following usecases:
What do you think?