|
Hi, I would happily give the headscale approach with your eap plugin a go. How do i configure it? Can I modify it, so I can insert an authkey already into the eap, and distribute it this way, that on install it connects directly to my headscale host? |
Replies: 2 comments 1 reply
|
Hey |
|
Thanks again, and sorry for the late reply. Everything is working as expected. ;) One question, regarding OS-13, and their requirement to get the acap apps signed (https://www.axis.com/for-developers/news/AXIS-OS-13-breaking-changes)), did you have that on your screen? Would you get this custom app certified? |
|
Glad to hear, ACAP signing is on my radar and one way or another all my acaps will be signed to comply with the new restrictions. More info soon. |
Hey
I would suggest you use it as intended by adding your auth key in the settings of the acap after installing, so if you change auth keys you dont have to rebuild the acap.
But if you really want you could modify the aarch64_custom/app/lib/start_tailscale.sh script with your server address and auth key instead of reading it from the config file on start up.