@@ -86,16 +86,22 @@ cargo test
86
86
```
87
87
88
88
Some tests require access to the database. To run them, set the
89
- ` CRATESFYI_DATABASE_URL ` to the url of a PostgreSQL database. If you are using
90
- the ` docker-compose ` environment to run tests against, see the
91
- [ Docker-Compose] [ docker-compose-section ] section for the default PostgreSQL URL.
92
- You don't have to run the migrations on it or ensure it's empty, as all the
93
- tests use temporary tables to prevent conflicts with each other or existing
94
- data. See the [ wiki page on developing outside docker-compose] [ wiki-no-compose ]
89
+ ` CRATESFYI_DATABASE_URL ` in ` .env ` to the url of a PostgreSQL database,
90
+ and set the ` AWS_ACCESS_KEY_ID ` , ` S3_ENDPOINT ` , and ` AWS_SECRET_ACCESS_KEY ` variables.
91
+ We have some reasonable default parameters in ` .env.sample ` .
92
+
93
+ For example, if you are using the ` docker-compose ` environment to run tests against, you can launch only the database and s3 server like so:
94
+
95
+ ``` console
96
+ docker-compose up -d db s3
97
+ ```
98
+
99
+ If you don't want to use docker-compose, see the
100
+ [ wiki page on developing outside docker-compose] [ wiki-no-compose ]
95
101
for more information on how to setup this environment.
102
+ Note that either way, you will need docker installed for sandboxing with Rustwide.
96
103
97
104
[ wiki-no-compose ] : https://github.com/rust-lang/docs.rs/wiki/Developing-without-docker-compose
98
- [ docker-compose-section ] : #Docker-Compose
99
105
100
106
### Docker-Compose
101
107
0 commit comments