You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The title of this issue follows the Feature Request: brief description of feature request format, e.g. Feature Request: Add a dark mode to the website
Would you like to work on this issue?
Description of the Feature Request
Currently, the "Set Up DotEnv" section is missing some instructions / inconsistent.
Acceptance criteria
[ ] Guide needs to be tell the reader to "cd" into the local TOP repository before asking the reader to run cp env.sample .env (make it clear env.sample is in the local repository directory)
[ ] Explicitly tell the reader to set postgress password with postgres=# \password YOURUSERNAME. That this password will be stored in the .env file in the instructions that follow. Then it should be more clear what the document means by "Then edit the newly created .env file to include your Postgres Username and Password." The Linux Installation Guide currently makes this sound optional.
Additional Comments
No response
The text was updated successfully, but these errors were encountered:
Checks
Feature Request: brief description of feature request
format, e.g.Feature Request: Add a dark mode to the website
Description of the Feature Request
Currently, the "Set Up DotEnv" section is missing some instructions / inconsistent.
Acceptance criteria
[ ] Guide needs to be tell the reader to "cd" into the local TOP repository before asking the reader to run
cp env.sample .env
(make it clearenv.sample
is in the local repository directory)[ ] Explicitly tell the reader to set postgress password with
postgres=# \password YOURUSERNAME
. That this password will be stored in the .env file in the instructions that follow. Then it should be more clear what the document means by "Then edit the newly created .env file to include your Postgres Username and Password." The Linux Installation Guide currently makes this sound optional.Additional Comments
No response
The text was updated successfully, but these errors were encountered: