## What
Adds new options for easier usage of the `create-medusa-app` command for regular medusa users.
The following options are added:
- `--skip-db`: Skips creating the database, running migrations, and seeding, and subsequently skips opening the browser. Useful if the developer wants to set the database URL at a later point in the configurations.
- `--db-url <url>`: Skips database creation and sets the database URL to the provided URL. Throws an error if can't connect to the database. Will still run migrations and open the admin after project creation. Useful if the developer already has database created, locally or remotely.
- `--no-migrations`: Skips running migrations, creating admin user, and seeding. If used, it's expected that you pass the `--db-url` option with a url of a database that has all necessary migrations. Otherwise, unexpected errors will occur. Helpful only if combined with `--db-url`
- `--no-browser`: Disables opening the browser at the end of the project creation and only shows success message.
- `--directory-path <path>`: Allows specifying the directory path to install the project in. Useful for testing.
* feat(create-medusa-app): added stable option
* add new function
* changed open url
* switch condition
* fix open url for stable
* add URI encoding
* modified db error message
* feat(create-medusa-app): update command for a better onboarding experience
* use medusa-telemetry for tracking
* update used snapshot
* added changeset
* update yarn.lock
* increased facts timer
* updated snapshot version
* show facts throughout installation + add first_run to url
* added message after server termination
* print message only once
* added github to process terminated message
* address pr feedback
* added onboarding seeding
* fix for npm install
## What
- Removed the `seed` process and the `--no-seed` option from the `create-medusa-app` command
- Improved the success message to include details about creating the database and running migrations before starting the backend.
## Why
As of removing support for SQLite, the `seed` command does not work most of the time on installation since there's no database configured and the default one isn't created by the user yet. This leads to an error message showing during the installation which leads the user into thinking the setup went wrong.
Also, the steps after the installation is done successfully don't include anything related to the database, which means that when the user starts the backend they'll see errors.
