Create the new project's .env #36

New Issue

2026-10-06T06:49:03+02:00

Tirsvad commented

2026-10-06 06:49:03 +02:00

After the local project exists and only after a yes (default no): write the needed keys to .env created with umask 077 and mode 600, never replacing an existing file without a yes, and add .env to .git/info/exclude. Report it in the summary without showing a value. A new lib/envfile.sh (class EnvFileWriter). Step 9 and extensions 9c and 9d of [UC-001].

Phase: MIL-005
Reference: [UC-001]

After the local project exists and only after a yes (default no): write the needed keys to `.env` created with `umask 077` and mode 600, never replacing an existing file without a yes, and add `.env` to `.git/info/exclude`. Report it in the summary without showing a value. A new `lib/envfile.sh` (class `EnvFileWriter`). Step 9 and extensions 9c and 9d of [UC-001]. Phase: MIL-005 Reference: [UC-001]

Tirsvad added this to the MIL-005 Credentials milestone 2026-10-06 06:49:03 +02:00

Tirsvad referenced this issue

2026-10-06 06:50:17 +02:00

Add the Design Class Diagrams and plan MIL-005 (credentials asked, project .env) #40

Tirsvad referenced this issue from a commit

2026-10-06 07:29:04 +02:00

Ask for missing credentials and create the project's own .env

Tirsvad referenced a pull request that will close this issue

2026-10-06 07:44:41 +02:00

MIL-005: ask for missing credentials and create the project's own .env #41

Sign in to join this conversation.