VWS-Python
diff --git a/‎.gitignore‎
Lines changed: 2 additions & 0 deletions b/‎.gitignore‎
Lines changed: 2 additions & 0 deletions
diff --git a/‎CONTRIBUTING.md‎
Lines changed: 4 additions & 5 deletions b/‎CONTRIBUTING.md‎
Lines changed: 4 additions & 5 deletions
@@ -92,6 +92,8 @@ ENV/
 
 # Files containing secrets
 vuforia_secrets.env
+vuforia_secrets_ci.env
+vuforia_secrets_ci_master.env
 
 # mypy
 .mypy_cache/
 
@@ -91,17 +91,16 @@ Set either `SKIP_MOCK` or `SKIP_REAL` to `1` to skip tests against the mock, or
 Tests are run on Travis CI.
 The configuration for this is in `.travis.yml`.
 
-Travis CI is set up with environment variables for connecting to Vuforia.
-These variables include those from `vuforia_secrets.env`.
+Travis CI is set up with secrets for connecting to Vuforia.
+These variables include those from `vuforia_secrets.env.example`.
+
 They also include another set of variables especially for running the tests on the `master` branch.
 The tests are run daily against the `master` branch.
 This means that when the daily request quota is used, the `master` branch may show as failing on the `README`.
 Using the request quota on the `master` branch also leaves fewer requests for regular development.
 Therefore, `master` is given its own Vuforia database with separate limits.
 
-These include the variables from `vuforia_secrets.env` prefixed with `MASTER_`.
-
-All targets are deleted from the database beween each test.
+All targets are deleted from the database between each test.
 Therefore there may be conflicts if the test suite is run concurrently as Travis CI is configured to connect to one Vuforia database.
 As such, Travis CI is configured not to run multiple instances of the test suite concurrently.