We are currently exposing the DB and Redis ports to the host, making the services externally accessible, which is very useful for a development environment.
`docker-compose` is however the only deployment method we currently support, and our Getting Started guide uses the very same configuration to guide users through the process of deploying open-balena on a public server (mostly because it’s easier with regards to DNS). This means we’re effectively guiding users to deploy open-balena in a very insecure way.
This commit removes host port bindings for the database and Redis services, effectively making them externally inaccessible.
Fixes#34
Change-type: minor
Vagrant machine is based on Ubuntu 18.04 including:
- docker
- docker-compose
Provisions some helper functions to the CLI:
- dc (shortcut to ./scripts/compose)
- enter {service} (opens a terminal in the service's container)
- logs {service} (access the journal of the service)
Change-type: patch
Signed-off-by: Rich Bayliss <rich@balena.io>
Fix versionist formatting error in CHANGELOG.md.
Also re-formatted previous changelog entries for consistency with the
new format.
Change-type: patch
Signed-off-by: Giovanni Garufi <giovanni@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
