-
-
Notifications
You must be signed in to change notification settings - Fork 4.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
Added Dockerfile #114
Added Dockerfile #114
Conversation
|
||
# We run index.js, but you should update this to the main | ||
# file defined in `main` in package.json | ||
CMD node index.js |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really we should have a default working sample app.js file somewhere and use that. The image built by this Dockerfile should have a runnable parse-server container with minimal efforts.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah... So, the parse-server-example is that, basically... and there's a Dockerfile there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The Dockerfile runs index.js which is the main file. I could add a test.js that creates an instance of ParseServer.
Also, parse-server-example does not have a Dockerfile.
Since this is just the router package, and not a full server, I think the Dockerfile should reside in parse-server-example. I just merged a PR there which added it. |
Fix destroyAll with useMasterKey option
See issue: #110