New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Allow to setup Graphjin with a pre-existing Postgres databse #382
Comments
This is a great point should be easy enough to add. |
I also would appreciate this |
New argument `-db-url` on the `new` sub-command allows you to point a new app to a local database. Eg. graphjin new testapp --db-url=postgres://user:pass@localhost/testapp-development
Just added support for this. Does this work you you'll?
|
Mhh i am probably doing something wrong, but its not working for me. makefile
New db use case:
existing Db use case:
|
Also for an existing DB use case, why gen a docker compose ? I would have thought a docker is enough and easier for people to deploy. I am using fly, and so a single docker is alot easier to work with on fly at least |
You're correct we probably don't need the docker-compose.yml when using an external db. I would suggest changing the If you still want to use docker-compose then just mke the below change to your docker-compoose.yml
|
I'm making the code change to ensure that when the |
Ok thanks @dosco will try again when it’s ready |
This has been comitted i'm closing this issue for now. |
Thank you. This is perfect. |
What would you like to be added:
Right now, in order to start Graphjin docker-compose pulls it and Postgres docker image as its dependency for the whole setup.
Unfortunately, there is no straightforward way of setting up Graphjin using a pre-existing database
A command like
That will create a docker-compose with only Graphjin as a service and point graphjin to already running postgres database (barebones on my machine or remote)
Why is this needed:
For adopting Graphjin in already running projects (databases)
Will save time to deliver products
The text was updated successfully, but these errors were encountered: