-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Create Dockerfile #303
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
Create Dockerfile #303
Conversation
It's bad practice to bake the environment variables into the image. I think @flovilmart is working on a CLI, which would make sense to use as the ENTRYPOINT. |
I'm effectively working on some CLI system and also support for multiple apps and cloud code instances. As a good side effect, we now have automated hooks registration upon declaration :)
|
@flovilmart I'd say even doing a
You can then pass commands to the image on dockerhub, i.e.
Could launch an instance of the server with 1 line. If you're feeling ambitious, the CLI could also manage installing/registering Parse modules, similar to how the |
@mysale01, I'm pretty new to docker, and yes copy the config.json is not possible as for the base image as it's not there :) As of today, the base CLI is there on master under |
@didierfranc updated the pull request. |
1 similar comment
@didierfranc updated the pull request. |
Can we create a |
Docker files have to be run at the project root because only subdirectories On Friday, February 12, 2016, Fosco Marotto [email protected]
|
👍 @maysale01 |
In that case, we'll close this. If there's use in having a simpler one, let us know. |
It should be good to have a Dockerfile here to have an automated image on docker hub from the official Parse-Server repo !