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
This does not work. When I declare a services.postgres.svc and another block in a different directory, it returns an error:
error: The option `services.postgres.service2' does not exist. Definition values:
- In `.../my_service1/devenv.nix':
Can devenv up be configured to merge configs of each PG instance? This would be similar to services-flake behavior here I think.
The use case I have in mind needs to enable a DB per service (1:1). All services are in a single repo, with a devenv.sh at the root and one per service. It would be sufficient if a single services.postgres could be started at the root, and multiple databases could be define via each service's respective devenv.sh.
How can I set it up using devenv.sh?
The text was updated successfully, but these errors were encountered:
Greetings,
What is the best current practice for the "DB per service" model using Devenv's monorepo support?
I currently have something like two
devenv.sh
files for two services:This does not work. When I declare a
services.postgres.svc
and another block in a different directory, it returns an error:Can
devenv up
be configured to merge configs of each PG instance? This would be similar toservices-flake
behavior here I think.The use case I have in mind needs to enable a DB per service (1:1). All services are in a single repo, with a devenv.sh at the root and one per service. It would be sufficient if a single
services.postgres
could be started at the root, and multiple databases could be define via each service's respectivedevenv.sh
.How can I set it up using devenv.sh?
The text was updated successfully, but these errors were encountered: