Explicitely tell where the .env file should be created #60
No reviewers
Labels
No labels
bug
dependencies
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: plume/documentation#60
Loading…
Reference in a new issue
No description provided.
Delete branch "plume/documentation:dot-env-location"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It was not clear to someone.
maybe we should provide a .env.example in the repo, and ask peoples to cp it, and modify things? That way it's position will probably be more clear
We should also consider the case where people don't clone the repo but use prebuilt binaries, but yes.
I still think we should have a .env.example filled with all supported env vars (commented out for most), but this is for another repository