Difference between revisions of ".env"
Jump to navigation
Jump to search
| (2 intermediate revisions by the same user not shown) | |||
| Line 2: | Line 2: | ||
=Sample .env= | =Sample .env= | ||
Please note that there should not be any white space characters between the <code>key</code>, <code>=</code>, and <code>value</code>. | Please note that there should '''not''' be any white space characters between the <code>key</code>, such as '''PORT_NUMBER''', <code>=</code>, and <code>value</code>, i.e. '''9352'''. | ||
<syntaxhighlight lang="Bash"> | <syntaxhighlight lang="Bash"> | ||
PORT_NUMBER=9352 | PORT_NUMBER=9352 | ||
MATOMO_PORT_NUMBER=32010 | |||
NC_PORT_NUMBER=32020 | |||
YOUR_DOMAIN=localhost | |||
</syntaxhighlight> | </syntaxhighlight> | ||
=References= | =References= | ||
Latest revision as of 09:44, 27 August 2021
The .env[1] is a file dedicated to specify configuration information for a software project. In the context of PKC, we will try to converge all configurable parameters to be stored in this file. Other than your secretive information, such as password and private keys to your related systems, this file will be the only file you will need to change to specify customized parameters for your own system.
Sample .env
Please note that there should not be any white space characters between the key, such as PORT_NUMBER, =, and value, i.e. 9352.
PORT_NUMBER=9352
MATOMO_PORT_NUMBER=32010
NC_PORT_NUMBER=32020
YOUR_DOMAIN=localhost