IMPORTANT!If you already had setup openBalena server you can skip this part to the Github Actions server preparation
$ docker-compose --version
.docker
group:quickstart
script as below. This will create a new config
directory and generate appropriate SSL certificates and configuration for the server. The provided email and password will be used to automatically create the user account for interacting with the server and will be needed later on for logging in via the balena CLI. Replace the domain name for the -d
argument appropriately.-d
argument spawns the containers as background services.<service-name>
with the name of any one of the services defined in compose/services.yml
; eg. api
or registry
.100.100.100.100
and your domain is mydomain.con
100.100.100.100
mydomain.con
config/certs/root/ca.crt
on the server. docker
group:github
user and run each shell command in the order shown.config
script to configure the self-hosted runner application and register it with GitHub Actions. The config
script requires the destination URL and an automatically-generated time-limited token to authenticate the request.systemd
, you can use the svc.sh
script distributed with the self-hosted runner application to install and manage using the application as a service.BALENA_API_TOKEN - Create balenaToken using CLI at your local machineOPEN_BALENA_ADDRESS - This must to point for your openBalena server address like mydomain.com NOT api.mydomain.comOPEN_BALENA_ROOT_CERT*IMPORTANT - ca.crt must to be inlined with \n symbolsUseawk 'NF {sub(/\r/, ""); printf "%s\\n",$0;}' ca.crt
to inline your crt file - copy output and paste it to value input.
balena push
analog with using open-source alternatives!