GitHub Actions not triggering anymore

[01110111000001]

Hello, first of all thank you very much for your work on rootless and distroless images as well as all the knowledge you shared!

1. As said in the issue title, it seems the actions to build this image are not triggered anymore. Is it voluntary ?
2. You may not be interested but I wanted to share how I modified the management config to use the embedded IdP (that can itself connect to external ones later if needed). This seems easier to deploy and requires less config to get started.
   To use the embedded IdP, one should remove the HttpConfig, IdpManagerConfig and PKCEAuthorizationFlow sections from the management.json file and modify the EmbeddedIdP section to look like this:

  "EmbeddedIdP": {
    "Enabled": true,
    "DataDir": "/netbird/etc",
    "Issuer": "https://${NETBIRD_FQDN}/oauth2",
    "DashboardRedirectURIs": [
      "https://${NETBIRD_FQDN}/nb-auth",
      "https://${NETBIRD_FQDN}/nb-silent-auth"
    ],
    "Storage": {
      "Type": "postgres",
      "Config": {
        "DSN": "${NETBIRD_STORE_ENGINE_POSTGRES_DSN} sslmode=disable"
      }
    }
  },

3. I also enabled the STUN server embedded in the "new" relay server.
   This removes the need for the TURNConfig section in the management.json
4. I'm not sure I understand the usefulness of the custom management executable you provide. The official one already uses the environment variables of the container to substitute them in the management.json file. Am I missing something ?

I'm totally open to share my config files if you are interested by my changes.

[11notes]

1. Not really, I switched to a global trigger since github disables crons after repo inactivity, I simply forgot to rename the workflow to update.yml, which is now corrected.
2. I’ve not yet tested the internal IdP, it gave me real trouble because it was using SQLite with a c-dependent library (even when using Postgres), which I could fix, but the example compose does not use it. I have a look if it is easier to use then just to use the keycloak example.
3. I missed that, thanks, Netbird moves quite fast, I will add it to the default config.
4. I think it didn’t a few versions back, I would also have to replace all code with go-eleven to streamline the whole thing, but having our own init system can be of use for example for inline compose configs.

Thanks anyway for the excellent feedback, I’ll update the repo as soon as I have time 😊.