This can be removed completely now — it was added to ensure existing users also update to the latest (at the time) CLI as they updated their open-balena installation.
Change-type: patch
In order to support the new CLI and balenaCloud deployment
schemes for the tunnel service, the service is now exposed via
the TLS port 443 on the `tunnel.{domain}` server name.
Change-type: patch
Signed-off-by: Rich Bayliss <rich@balena.io>
Update open-balena-s3 to 2.8.3
This makes new installations of openBalena use the S3 container as a
storage backend for the Registry service by default. Existing installs
should not be affected.
Change-type: major
Signed-off-by: Rich Bayliss <rich@balena.io>
- remove some `.gitignore` entries as this is also honoured by `balena push`
- added a step to `scripts/quickstart` to produce a single, flat `docker-compose.yml` after running
- set the compose file versions to `2.0` to ensure only supported terms are used in the `docker-compose.yml` file output
- quoted empty env values as these need to be passed in as blank, and not ommitted
- include the MDNS publisher service IF the domain being used is a .local one
- corrected spelling of macOS in script messages
- move sidecar container source into ./src as per convention
Change-type: patch
Signed-off-by: Rich Bayliss <rich@balena.io>
For convenience, also add instructions what to install.
Tha change also addresses invalid usage of 'local' outside of a function.
Change-type: patch
Signed-off-by: Roman Mazur <mazur.roman@gmail.com>
The VPN CA shouldn't need to be signed by the same CA that the HAproxy service
certificate is signed by. By removing this chain we are able to use a
different CA for the HTTPS services without impacting on the VPN service.
Change-type: patch
Signed-off-by: Rich Bayliss <rich@balena.io>
In order to have concrete releases of openBalena we should pin each
service to a given version. This PR is the start of this and marks
the first version of openBalena with known service tags.
Change-type: major
Signed-off-by: Rich Bayliss <rich@balena.io>
Add a service which will acquire certificates from an ACME cert
provider, such as LetsEncrypt (), to allow an openBalena instance
to use a publicly trusted certificate instead of the self-signed
one it wil generate on setup.
Change-type: patch
Signed-off-by: Rich Bayliss <rich@balena.io>
Allows the credentials to be passed via the environment in order
that the application can create the user on start up.
Change-type: patch
Signed-off-by: Rich Bayliss <rich@balena.io>
NodeJS is installed as `nodejs` in some distros, `node` in others. This ensures we can find either one or fail with a proper error, and also documents that NodeJS is required in the first place.
Fixes: #5
Change-type: patch