Hello, just a friendly nudge. I'm available to chat via email/matrix/anything else if you have any questions!

@avicenzi, @mcaj: review reminder

The service requires a file /etc/netbird/config.json, where does this come from?

Is this created by the service once you start? If yes, all good. Do I need to create one first? If yes, a template should be provided. Do I need to run a command? If yes, it would be nice to include in the README or other documentation bit.

If this file is required prior to the service start, adding an assert to ensure that the file exists will give a better error message.

Yep--it is created by the service. Just tested in a fresh kiwi-generated TW VM to be sure. Fresh install has empty /etc/netbird directory, and on enabling/starting the systemd service, it auto-generates the config file. Most of the configs are modified through the netbird UI (e.g. netbird up --management-url <your-netbird-server> -k <persistent-setup-key>) which then modifies the config file accordingly.

Only thing my patch disables is the actual systemd service file generation, as it relies on a go library (https://pkg.go.dev/github.com/kardianos/service#section-readme) that generates service files that...aren't the best. And then a couple messages so the user is aware of this fact in the build--in case they try to run netbird service install or similar.