raggedstaff/openfoodnetwork
1
0
Fork 0
mirror of https://github.com/openfoodfoundation/openfoodnetwork synced 2026-01-11 18:26:50 +00:00
Code Issues Packages Projects Releases Wiki Activity

Only the .env.test.local file (not tracked) should be changed

Browse Source 
This prevents contributors from inadvertently committing changes on the .env.test file (which is tracked)

Reverts changes to .env.test and changes README.md accordingly
This commit is contained in:
filipefurtad0
2025-07-10 11:07:26 +01:00
committed by Filipe
parent 352f1ba900
commit 38388be4da
2 changed files with 1 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
.env.test
View File

@@ -35,6 +35,3 @@ OPENID_REFRESH_TOKEN="dummy-refresh-token"
ACTIVE_RECORD_ENCRYPTION_PRIMARY_KEY="test_primary_key"
ACTIVE_RECORD_ENCRYPTION_DETERMINISTIC_KEY="test_deterministic_key"
ACTIVE_RECORD_ENCRYPTION_KEY_DERIVATION_SALT="test_derivation_salt"
# Let the tests know if they are run within a Docker container:
# DOCKER="true"

2
docker/README.md
View File

@@ -5,7 +5,7 @@ Docker is intended to provide a common virtual environment available to all deve
## Limitations
1. The docker environment can't directly control your host system browser, which means that browser specs (under `/spec/system/`) and email previews will not work. You may be able to find a solution with [this article](https://evilmartians.com/chronicles/system-of-a-test-setting-up-end-to-end-rails-testing). If so, please contribute!
2. You can try circumventing this by setting the option `DOCKER=true` on the `.env.test file`, which will disable the `sandbox` mode for Chrome, used for system tests.
2. You can try circumventing this by setting the option `DOCKER=true` on the `.env.test.local` file, which will disable the `sandbox` mode for Chrome, used for system tests.
## Installing Docker
### Requirements