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
Is there an existing issue that is already proposing this?
I have searched the existing issues
Is your feature request related to a problem? Please describe it
mantis-app init assumes you have a db url ready. Many users of this cli won't have it ready or will cancel creation thinking mantis is too complicated.
Describe the solution you'd like
mantis-app init should give the user an option to choose how the database is created. It should be one of these options to start with:
- prompt the user if they want to provide their own mongo connection string or if a local db should be created
- in the case the user selects the latter, scaffold the generated project will create a local mongodb with data persisted to disk
- add mongodb-memory-server to accomplish the above
- this is used for in memory e2e testing, but can be configured for local persistence
- this dependency will be handy for when we create e2e tests
- use a tmp dir for the dbPath
- if the user creates multiple workspaces with the same project name, the dbPath will collide
- this is fine for now
Closes#28
Is there an existing issue that is already proposing this?
Is your feature request related to a problem? Please describe it
mantis-app init
assumes you have a db url ready. Many users of this cli won't have it ready or will cancel creation thinking mantis is too complicated.Describe the solution you'd like
mantis-app init
should give the user an option to choose how the database is created. It should be one of these options to start with:Teachability, documentation, adoption, migration strategy
No response
What is the motivation / use case for changing the behavior?
A db is the only component that needs to be user provided during
mantis-app init
. Automating this will make the "init" experience seem "magical".The text was updated successfully, but these errors were encountered: