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 .env file is mandatory for the project to build, however it is intentionally not provided as part of the project as it will contain the project secrets. The Chapter developer/installer is required to issue the proper commands to create and edit the .env file.
A script has been provided to copy defaults values from the .env.example into the .env .
Put the following sentence into the CONTRIBUTING.md file around line 310 in
the section run the app step 1.
Run npm run postinstall to copy the file .env.example into the file .env.
If the .env file exists it will not be overwritten.
Describe the bug:
The .env file is mandatory for the project to build, however it is intentionally not provided as part of the project as it will contain the project secrets. The Chapter developer/installer is required to issue the proper commands to create and edit the .env file.
A script has been provided to copy defaults values from the .env.example into the .env .
Put the following sentence into the CONTRIBUTING.md file around line 310 in
the section run the app step 1.
Tell us about your browser and operating system:
uname -ior
5.3.7-301.fc31.x86_64 x86_64 GNU/Linux