1.3.0

What's Changed

• User management UI for admins by @brunojppb in #33
• Bump to version 1.3.0 by @brunojppb in #34

Improvements in the Admin UI

You can now lock user accounts, which prevents them from signing in and create teams and/or tokens. You can also change their system role between user and admin.

Full Changelog: 1.2.0...1.3.0

1.2.0

What's Changed

• Heex formatter plugin by @brunojppb in #29
• App Settings by @brunojppb in #28
• Update README by @brunojppb in #30
• Health check endpoint by @brunojppb in #31
• Bump version to 1.2.0 by @brunojppb in #32

Admin Settings UI

You can now control whether users can create accounts on Turbo Racer. This is an important feature if you are deploying Turbo Racer to a public network and don't want anybody else creating accounts.

• If you are deploying Turbo Racer for the first time, the first user signup will be automatically assigned with the admin role.
• If you have users already registered to your instance, the first user will be automatically assigned the admin role and will be able to access admin settings where they can toggle this configuration.

Health check endpoint

There is now a dedicated health check endpoint under /management/health that performs a simple check against the db/cache. It will be improved later on, but it's good enough for now to report server healthiness.

Full Changelog: 1.1.0...1.2.0

1.1.0

What's Changed

• Scope artifact uploads under a team directory by @brunojppb in #26
• Bump version to 1.1.0 by @brunojppb in #27

Artifact storage updates

Before version 1.1.0, artifacts were being stored on a flat directory. Although I've not seen hash collisions, given the team permissions around artifacts access in Turbo Racer, different teams (Using different TURBO_TEAM variables) working on the same codebase could generate the same output hash for any given task.

To allow teams being fully independent at the artifact caching level, I've chosen to scope artifacts under a team directory (e.g. team_1/random-hash-here), so previously generated artifacts need to either be migrated and scoped under a team_<team_id> folder or deleted entirely. The simplest way is to just bust all artifacts from your storage (either S3 or local file system) and the artifacts table and let your users generate the caches again.

Full Changelog: 1.0.8...1.1.0

1.0.8

What's Changed

• Add Open Graph tags and document how to use environment variables with Turbo by @brunojppb in #24
• Bump to 1.0.8 by @brunojppb in #25

Full Changelog: 1.0.7...1.0.8

1.0.7

What's Changed

• Use port 443 in production when HTTPS is enabled by @brunojppb in #22
• Bump to version 1.0.7 by @brunojppb in #23

Full Changelog: 1.0.6...1.0.7

1.0.6

What's Changed

• Elixir 1.14 by @brunojppb in #20
• Version bump to 1.0.6 by @brunojppb in #21

Full Changelog: 1.0.5...1.0.6

1.0.5

What's Changed

• #18: Delete Artifacts from data store before deleting teams fixing #17
• #19: Bump to v1.0.5

Docker images

You can run Turbo Racer via Docker using our amd64 and arm64 images available here.

Full Changelog: 1.0.4...1.0.5

1.0.4

Make sure that the SSL app starts when running migrations against SSL-protected database URLs add178c

Docker images available

You can use our Docker image built for production directly from Dockerhub here.

For a full production setup, have a look at the docker-compose.prod.yml file in the repo.

Full Changelog: 1.0.3...1.0.4

1.0.3

What's Changed

• Add Digital Ocean deployment template by @brunojppb in #14
• Fix Digital Ocean YML template by @brunojppb in #15
• Add option to enable database SSL connection with Postgres by @brunojppb in #16

Docker images available

You can use our Docker image built for production directly from Dockerhub here.

For a full production setup, have a look at the docker-compose.prod.yml file in the repo.

Full Changelog: 1.0.2...1.0.3

1.0.2

What's Changed

• Remove DB waiting checks as compose file already does it by @brunojppb in #13

Full Changelog: 1.0.1...1.0.2