Rolling out a self-hosted Infisical

Back in July I compared Bitwarden Secrets Manager to Infisical [https://www.mikestreety.co.uk/blog/comparing-bitwarden-secrets-manager-to-infisical/]. Since then we've been running a self-hosted version of Infisical which, after a bit of setup, has been quietly providing our secrets ever since. Before committing to anything, we had a couple of requirements for whatever secrets manager we picked: * It shouldn't add mountains of setup or extra commands for our developers * Client servers shouldn't need anything installing for us to use it Infisical ticked both boxes. Locally, it's one extra word in front of a command developers already run, and for production, GitLab CI generates the .env file and drops it on the server, so there's nothing for the client's server to install or know about. USING INFISICAL Each project has a .infisical.yaml (or .infisical.json) file containing the Infisical project ID it's associated with. To start DDEV with the secrets loaded, our developers run:…