Tech stack

Basically any software forge…

…is composed of:

• a Version Control System (VCS): to host and version the code of our applications, scripts, infrastructure descriptions, pretty every source code.

• a CI/CD service: to run jobs automatically for tests of one-off executions of versionned code.

• a Secret Manager: to inject secrets into jobs and give the access to specific environnements or permissions.

• a Artifact Repository: to archive the outputs of our jobs if necessary.

The assembly of these functions or services form a CI/CD pipeline.

The Galaxie-Forge brew

• Gitea as our Version Control System (well Git, but you got the idea).

• Concourse as our continuous thing-doer.

• Hashicorp Vault as our Secret Manager

• Gitea has built-in Package registry and Container Registry features, so it’s our Artifact Repository.

All these components require some work and maintenance to fit together. We address this issue by building this project’s code base to:

• deploy

• operate

• maintain

We rely on:

• Ansible

• Terraform

• Packer

Platform support

Our first goal is to be deployable on a personnal Debian workstation.

Next we aim to support these IaaS providers (in this order):

• Proxmox

• Scaleway

• AWS