rapenne-s / bento Goto Github PK

For example I use a nixos config flake like this starter template:

https://github.com/Misterio77/nix-starter-configs/tree/main/standard

I tried it locally and I think maybe not?

I know you mentioned this a while back here: https://discourse.nixos.org/t/introducing-bento-a-nixos-deployment-framework/21446/27

I am deploying from ts-bento-nixos. I have two other hosts configured and deployments work. However, when I run bento status after deploying I get the following:

       machine   local version   remote version              state                       elapsed time since
       -------       ---------      -----------      -------------                            -------------
awk: fatal: cannot open file `states.txt' for reading: No such file or directory
grep: states.txt: No such file or directory
ts-bento-nixos      non-flakes      nbc3bplm 📌      up to date 💚                          (build 19m 11s)
awk: fatal: cannot open file `states.txt' for reading: No such file or directory
grep: states.txt: No such file or directory
   ts-subnet-a      non-flakes      5i516yif 📌      up to date 💚                           (build 3m 22s)
awk: fatal: cannot open file `states.txt' for reading: No such file or directory
grep: states.txt: No such file or directory
   ts-subnet-b      non-flakes      wdm9ql6v 📌      up to date 💚                           (build 4m 48s)

Also, bento status 5 does not give a delay between status updates.

Thanks for your help!

Is there a reason why the config is build locally on the deployment server?

The only reason I can think of is to check for build errors. But if I see it correctly, the nixos-rebuild happens locally on the client, right? So if something would be wrong with the config, the client would return an error code?

My use case is:
I have a deployment server for several machines with a mixture of aarch64-linux and x86_64-linux and rebuild for every machine takes quite a while. It would speed up the process immensely if the config doesn't need to be build by the deployment server every time.

Hi! I was pointed to Bento as a simple and effective solution to deploying NixOS configurations. However, one of my servers is aarch64-linux and isn't supported by Bento (I can't run nix shell github:rapenne-s/bento).

It doesn't look like Bento depends on anything x86_64 specific. Could support be added easily?