make env-prepare
Introduction
make env-prepare makes sure the workspace .env exists and is correct. make setup and make docker-up run it for you. Run it alone to create the .env of a fresh clone without starting Docker.
make env-prepare
🛠️ SPLENT fix-workdir
• Created .env from .env.example
[✔] SPLENT_HOST_PROJECT_DIR set to /home/me/splent_workspace
[✔] WORKING_DIR already correct (/workspace)
🛠️ SPLENT fix-app
[✔] No product selected (already detached), nothing to fix
What it runs
fix-workdircreates../.envfrom the committedsplent_cli/.env.examplewhen it is missing. Then it setsSPLENT_HOST_PROJECT_DIRto the real host path andWORKING_DIRto/workspace.fix-appclearsSPLENT_APPwhen it names a product folder that does not exist.
Every other key is kept. See how the repairs write .env.
Adding your credentials
It never fills in SPLENT_FORGE_TOKEN or TWINE_PASSWORD. Add them to ../.env by hand, or run these inside the container.
splent env:set forge
splent env:set pypi
See env:set.
See also
make env-checkvalidates without changing anything.make fix-envrepairs, then validates.