Use docker compose to run database in development

[SidneyNemzer]

This change allows developers to run yarn dev and, assuming docker is installed, the database will start before running the api servers.

If you don't have docker, the dev scripts will fail. Let me know if you think docker is a reasonable dependency. I could make the new scripts exit early if docker is not detected.

[Nudelsuppe42]

Theoretically you dont need the individual scope#script scripts as turbo will automatically only run the script in projects where the script exists (eg. db:migrate only exists in @repo/db)

[SidneyNemzer]

@Nudelsuppe42 Ah good point. Should I remove the scopes? I will say, it's nice that the scope makes it clear the script only runs in one package. But happy to remove them.

[Nudelsuppe42]

What about putting frontend:dev with turbo run dev --filter=frontend... in the package.json? That way we only have the core scripts in turbo.

[SidneyNemzer]

Added dev:frontend since we already have build:api and build:frontend. What do you mean by core scripts?

[Nudelsuppe42]

I meant dev, build, etc.

[SidneyNemzer]

Does this need any other changes or is it ready to merge you think?

[Nudelsuppe42]

Also, i'd remove the changes in turbo.json. The PG stuff looks good to me

[SidneyNemzer]

Also, i'd remove the changes in turbo.json. The PG stuff looks good to me

You mean the scope prefixes? Just removed them. I think I can't totally remove the scripts from turbo.json because of the dependency order (up -> wait -> migrate -> dev)