Document secrets/.env usage #281
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Andras/BoundlessFlowCampus2K#281
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
We need to create a wiki page documenting how, why and when to use the secrets/.env file for those who haven't used it previously, since it hasn't been brought up much in our program.
Add documentation to this wiki page: Secrets and .env.
Feel free to change name of wiki page.
Parent Issue: #11
Related Issue: #239
The documentation has been added to wiki
The structure is clear and follows a logical flow through out the document. With steps explaining what a .env file is and then explaining how it works within the project. this makes the content easy to follow and understand.
However an issue is that the page basically only contains information on how it works and is used. So the page would benefit from explaining why we are using this approach and When we should use it. This will hopefully help make the page slightly more beginner-friendly and easier to understand for developers who may not be familiar with .env.
Why use an .env file
We use an .env file to separate configuration values from the code.
When to use .env file
I will update wiki with this when the review is done
Great job.
The update clearly addresses the missing context from the original documentation. And the page now clearly explains what an .env file is, how it works, why its used and when to use it.
Therefore I believe that the documentation is now complete and fit for use.