Blog
Ephemeral environments, explained
Ephemeral environments on plain Docker: how they work, what they are for, and how to run them yourself.
Local code, remote stack
Your whole stack runs on the team's Docker hosts. Your code, debugger and tools stay on your laptop and reach it on localhost. One CLI, nothing else to install.
One environment per pull request
The fadebox CLI in GitHub Actions and GitLab CI: an instance per pull request on its own URL, the suite reporting what it found, torn down when the PR closes.
One feature, start to finish
One feature followed through a team's lifecycle, branch to hotfix, and where Fadebox fits at each step: the PR copy, review, QA, release, support.
Your first environment: PetClinic on Fadebox
A database from the catalog, a template you write for a real app, an environment composing both, and an instance on a URL. Plus: templates versus the catalog.
Install Fadebox on your laptop
Two containers, one .env file and a wildcard domain that needs no DNS: Fadebox on your own machine to try it, and the three things that change on a real server.