load server apikey if configured

[0xbrayo]

Adds support for auth, which will be released in the new version of AW.

[2e3s]

Hello, thank you for the update! This needs to be implemented indeed. Just a couple things

• What if the server is not local? (docker/VM/another host)
• Not sure about taking in aw-server (outside of the bundle) just to read the existing TOML file... Might just read the file in the expected place, take auth_key and be done with it.

[0xbrayo]

* What if the server is not local? (docker/VM/another host)

You can have user set the apikey and host in a config file. With that apikey taking precedence over any discovered apikeys.

I thought directly depending on aw-server would be cleaner, incase the paths or any other config related stuff changes, directly reading the apikey works too :).

[0xbrayo]

perhaps even support for a cli flag --apikey or --authkey, feel free to modify the PR

[2e3s]

Okay, thank you, I'll reflect on it and adjust the code later, with a following release.

[2e3s]

I thought directly depending on aw-server would be cleaner
incase the paths or any other config related stuff changes

• It might involve more work for distro packaging,
• also inflate the binary size for the simplest functionality
• the compatibility would still be vulnerable because aw::config::whatever_method may change its signature or go private
• even the config path would depend on the aw-server commit hash, e.g. if you update the server, awatcher would still read it from the old place until you update the referenced commit hash. Might as well update the new path reading instead of updating the referenced hash.