Docker Compose file is now stored in compose.yaml

[jycouet]

Closes: #736

[changeset-bot]

🦋 Changeset detected

Latest commit: f1a7ea2

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
sv	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[pkg-pr-new]

Open in StackBlitz

npx https://pkg.pr.new/sveltejs/cli/sv@737

npx https://pkg.pr.new/sveltejs/cli/svelte-migrate@737

commit: f1a7ea2

[Conduitry]

We should be checking whether either file exists before going ahead and creating compose.yaml. We don't want to create compose.yaml if someone already has a docker-compose.yml. While we're at it, we should maybe also check for docker-compose.yaml.

[jycouet]

We should be checking whether either file exists before going ahead and creating compose.yaml. We don't want to create compose.yaml if someone already has a docker-compose.yml. While we're at it, we should maybe also check for docker-compose.yaml.

Thank you for looking and the feedback.
I could probably do quick fixes taking this into account, but maybe we should do one step back and rethink a few things.

In random order:
F. Our tests should have failed with my small change.
E. When a docker-compose.yml existed, we don't modify it, and we don't tell anything to the user
Y. We now have a yaml parser, we could edit xxx.yaml config
A. Drizzle add should add a first db. But when you run it a second time should it add a second db, or cancel (and explain)? (we speak about it here: #704 (comment) would be great to have your view)

[jycouet]

I'll close here in favor of this one: #738
It's taking into account your requests @Conduitry 👍
Thx