ExternalVendorCode/devilbox
1
0
Fork 0
mirror of https://github.com/cytopia/devilbox.git synced 2025-06-05 00:50:56 +00:00
Code Issues Actions Packages Projects Releases Wiki Activity

Fixes #145: Documentation for how to handle multiple env files

Browse Source
This commit is contained in:
cytopia 2018-04-25 00:41:13 +02:00
parent ba233165ab
commit 18a07a15f7
No known key found for this signature in database
GPG Key ID: 6D56EDB8695128A2
1 changed files with 11 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

15
docs/getting-started/best-practice.rst
View File

@ -155,16 +155,23 @@ In case of the Devilbox ``.env`` file, just store this file in your repository a
the Devilbox git directiry. This way you make sure that you keep your file, even when the Devilbox the Devilbox git directiry. This way you make sure that you keep your file, even when the Devilbox
git directory is deleted and you also have a means of keeping track about changes you made. git directory is deleted and you also have a means of keeping track about changes you made.
You could also go further and have several ``.env`` files available somewhere. Each of those files
holds different configurations e.g. for different projects or customers.
* ``env-customer1``
* ``env-php55``
* ``env-project3``
You would then simply symlink one of those files to the Devilbox git directory.
Version control service config files Version control service config files
------------------------------------ ------------------------------------
.. todo:: This will require some changes on the Devilbox and will be implemented shortly. .. todo:: This will require some changes on the Devilbox and will be implemented shortly.
* Symlink and have your own git directory
symlink and have your own git directory * Separate data partition, backups
Separate data partition, backups
PHP project hostname settings PHP project hostname settings