-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
Docker setup difference. #3954
Comments
Not a dumb question @samuelcastro Option one - docker compose - works really well for simple local setups and deploying on a single server like Digital Ocean. Basically, you'll have Hasura, Postgres + any other containers all wrapped up in a single The second option is just a shell script wrapping the raw Personally, I love using docker-compose. It's just so darn simple and works a treat for the types of apps I build. I use it when working with Docker containers locally, and sometimes in production if I realistically don't need to worry about multiple-containers running on multiple servers with a separate database / load balancer etc etc. Hope this helps a bit! |
Thanks @toddheslin helped a lot! :) |
This might be a dumb question, but what's the difference and why there are 2 difference Docker setup?
1 - https://docs.hasura.io/1.0/graphql/manual/getting-started/docker-simple.html#step-1-get-the-docker-compose-file (docker-compose)
2 - https://docs.hasura.io/1.0/graphql/manual/deployment/docker/index.html (docker-run.sh)
Would the
docker-run.sh
setup be more recommend for a production environment? If so why?Thanks!
The text was updated successfully, but these errors were encountered: