-
Notifications
You must be signed in to change notification settings - Fork 0
Runtime Config Requirements
The tool uses a github package and checks/pulls the main helium-rak Nebra Balena fleet repo
The only credentials you'll need to provide are API keys from your Balena account to give the tool access to push the changes from Github to your fleet directly. To do so you can obtain the keys via Balena Dashboard via your account preferences page. Then select the Access token tab, create a new token
You'll need to paste your API token into the console of this automation tool during your first execution. The configuration after completed then saves the settings you pasted into it. I should also mentioned that the token is not saved plaintext BUT it is saved in a way that someone - if they did get ahold of your config; could obtain your token without much effort needed. So PLEASE keep the machine/container you're running this on safe from someone's ability to freely read your files without your permission/access.
Upon you running this tool for the first time you'll be prompted for the credentials mentioned above.
Initial configuration steps
- API Token
- Discord Webhook Notification URL - THIS IS AN OPTIONAL SETTING, enter nothing if you do not wish to use this feature
- Balena fleet name - This can be obtained via Balena Dashboard
Once that is entered (correctly) your automation tool with now start and will continue to stay running until you tell it to end.
No problem, simply delete the config file that was saved and you'll be prompted to enter the credentials again.