-
Notifications
You must be signed in to change notification settings - Fork 48
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Introduced support of the .env for the local development (#537)
* Introduced support of the .env for the local development * Update the documentation
- Loading branch information
1 parent
b9109ce
commit 16517a0
Showing
9 changed files
with
29 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,20 @@ | ||
# Passing Vulnerable Secrets for Local Development | ||
|
||
This document explains how to use a **.env** file **for the local environment**. | ||
|
||
## Configuring .env | ||
|
||
1. Navigate to the **root directory of your project** and create a file named **.env**. | ||
2. Set up the necessary secrets for your environment. | ||
3. Bootstrap the Docker SDK: | ||
```bash | ||
docker/sdk boot {deploy file name} | ||
``` | ||
4. Start the local project: | ||
```bash | ||
docker/sdk up | ||
``` | ||
|
||
Once the project is running, all secrets from the .env file will be accessible to all Spryker applications, such as Backoffice, Yves, etc. | ||
|
||
**Note:** Ensure that **.env** is added to **.gitignore** (if not already) to prevent committing vulnerable secrets to the repository. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters