Linux development environment
Prepare a Linux machine to run SPLENT. You need Docker Engine with Compose v2, GNU Make and Git. A forge account is optional, since every repository is public and the CLI clones over HTTPS without one.
Table of contents
- Install Docker Engine
- Install GNU Make and Git
- Configure Git
- Configure forge access (optional)
- Verify your environment
Install Docker Engine
Install Docker Engine and the Compose v2 plugin with the official guide for your distribution. Then start the daemon and check that docker compose answers.
sudo systemctl enable --now docker
docker --version
docker compose version
Run Docker without sudo
The CLI talks to the Docker daemon as your user, so add yourself to the docker group.
sudo usermod -aG docker $USER
newgrp docker # or log out and back in
docker ps # should work without sudo
Install GNU Make and Git
# Debian / Ubuntu
sudo apt update && sudo apt install -y make git
# Fedora
sudo dnf install -y make git
# Arch
sudo pacman -S --needed make git
Configure Git
The CLI container mounts your ~/.gitconfig and ~/.ssh. If ~/.gitconfig does not exist, Docker creates it as an empty directory, and Git fails inside the container. Create the file and set your identity.
touch ~/.gitconfig
git config --global user.name "Your Name"
git config --global user.email "your_email@example.com"
Check that it is a regular file.
ls -l ~/.gitconfig
If
lsshows a directory (the line starts withd), remove it and create the file again.rm -rf ~/.gitconfig touch ~/.gitconfig git config --global user.name "Your Name" git config --global user.email "your_email@example.com"
Configure forge access (optional)
Every repository on git.splent.io is public. The CLI clones over SSH when your key is registered there and over anonymous HTTPS otherwise, so the installation and the tutorials need no account.
You need an account only to push your own repositories and publish features. Registration is closed, so ask the SPLENT maintainers for one.
SSH key
~/.ssh must exist and hold a key registered on the forge. The forge answers SSH on port 2223.
ls -ld ~/.ssh # must exist as a directory
ssh-keygen -t ed25519 -C "your_email@example.com" # if you have no key
cat ~/.ssh/id_ed25519.pub # add it on git.splent.io → Settings → SSH / GPG Keys
ssh -T -p 2223 git@git.splent.io
If
~/.sshdoes not exist on the host, Docker mounts an empty directory and the CLI clones over HTTPS.
API token
Releasing needs a forge token. Create one on git.splent.io under Settings → Applications → Access Tokens with the scopes write:repository and write:organization. Set SPLENT_FORGE_USER and SPLENT_FORGE_TOKEN in the workspace .env, which make setup creates next to splent_cli/. Inside the container, splent tokens:setup walks you through it and splent check:forge checks it.
Verify your environment
Once splent_cli is cloned (see Getting started), run the host pre-flight from splent_cli.
make preflight
It checks that Docker is installed and running, that Compose v2 is available, and that ~/.gitconfig and ~/.ssh are fit for the container. On a new workspace it also reports that the workspace .env does not exist yet, which make setup creates.
When everything passes, continue with Getting started.