-
Notifications
You must be signed in to change notification settings - Fork 73
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
Dockerfile #147
Comments
Would be great to see a standard docker image that could be used to deploy along with SurrealDb for development purposes. |
I'm struggling to see the necessity of a docker image considering Surrealist can already be accessed universally as a web app (surrealist.app), or installed locally as desktop app. Which benefits will a docker image provide over the existing deployment targets? |
@macjuul, while I haven't tried the Docker approach yet, I can think of a couple of reasons:
I'm not arguing these reasons are valid enough to merit an official Docker image, but if I were part of Unfortunately, for a production-ready app, |
It would be a benefit to deploy your own instance, so that you don't have to rely on the web app and you have the control about what is running. Also not everyone need to install a separate app and keep it updated. I would be nice to have something like pgadmin for surrealDB, which could be surrealist. |
Hello |
Thanks for the feedback everyone! I hear you, and will spend some time researching the viability of publishing an official docker image in the near future |
This one for webapp hosting:
And compose like this(with traefik)
It seems that surrealist access db thru a browser, doesn't work for compose hosts. |
Hi, I'm the author of the Nuxt has something called DevTools that expose a number of Nuxt utilities for managing the current project during development. I had plans to add A self-hosted Surrealist image would let developers opt-in and simplify their work. |
Describe the bug
here is a working dockerfile maybe you help me improve it
To Reproduce
Expected behavior
docker build .
docker run
Environment (you can view the current version under Settings):
The text was updated successfully, but these errors were encountered: