You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Any time you want to re-setup your databases (i.e. you run `docker-compose down`) - you will need to run that command pointed at the right YAML.
15
+
Any time you want to re-setup your databases (i.e. you run `dockercompose down`) - you will need to run that command pointed at the right YAML.
16
16
17
17
## Compile and Test
18
18
To start the build and run tests, its often best to skip the codegen tests as they can sometimes cause phantom errors. To do this, execute the following:
19
19
20
-
`docker-compose -f docker-compose-m1.yml run sbt sbt -Dmodules=db test`
20
+
`dockercompose -f docker-compose-m1.yml run sbt sbt -Dmodules=db test`
21
21
22
22
Drop the `-Dmodules=db` if you want to run ALL the tests (and grab an adult beverage while it runs - it'll be a while). Check out the `build.sbt` for a list of the
23
23
various modules you can build together or independently.
24
24
25
25
## Stop Your Services - Don't Down them!
26
-
Be nice to your M1 system - stop your services - don't down them. Running `docker-compose -f docker-compose-m1.yml down` will stop AND remove all your services. What this means is the next time you want to run your tests again - you better run setup again or your tests will fail due to missing databases!
26
+
Be nice to your M1 system - stop your services - don't down them. Running `dockercompose -f docker-compose-m1.yml down` will stop AND remove all your services. What this means is the next time you want to run your tests again - you better run setup again or your tests will fail due to missing databases!
27
27
28
-
If you plan to have some rapid build/test cycles - run: `docker-compose -f docker-compose-m1.yml stop` to stop your services. It will preserve the volumes that were created when you ran setup. It'll save you a good amount of time.
28
+
If you plan to have some rapid build/test cycles - run: `dockercompose -f docker-compose-m1.yml stop` to stop your services. It will preserve the volumes that were created when you ran setup. It'll save you a good amount of time.
29
29
30
30
## Build With a Specific Scala Version
31
31
By default the build executes with Scala 2.13. Not horrible - but if you want to take advantage of the improved compiler of a more recent 2.x version of Scala you can specify that!
32
32
You can simply set the `quill.scala.version` when you start your build:
33
33
34
-
`docker-compose -f docker-compose-m1.yml run sbt sbt -Dquill.scala.version=2.13.6 -Dmodules=db test`
34
+
`dockercompose -f docker-compose-m1.yml run sbt sbt -Dquill.scala.version=2.13.6 -Dmodules=db test`
35
35
36
36
Check out the [CONTRIBUTING](../../docs/CONTRIBUTING.md) guide for more details. Good luck!
0 commit comments