-
Notifications
You must be signed in to change notification settings - Fork 1k
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
New dockerfile and start script #871
Conversation
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.
LGTM, just one minor nitpicking comment
Dockerfile
Outdated
RUN ./installUbuntuDeps.sh --cleanup && \ | ||
./installErizo.sh && \ | ||
./../nuve/installNuve.sh && \ | ||
./installBasicExample.sh |
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.
please check indentation
…o fix/dockerStartScript
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.
Just a comment
sleep 3 | ||
} | ||
|
||
run_mongo() { |
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.
Perhaps we can reuse the code in /scripts/installNuve.sh by passing parameters depending on the parts we want to execute. If so we should split the populate code in that scripts in two parts: run mongo and populate mongo.
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.
I agree that we're duplicating code here, but I would do it as a part of a bigger refactoring of the scripts. Right now the populating the database is tied to copying the configuration and that can cause all sorts of problems if we make it an option in the default scripts.
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.
👍
Description
This PR implements a new Dockerfile and docker init script.
Instead of pulling the repository, the new dockerfile uses
COPY
to generate the context for the build.The new script allows for starting different parts of licode as well as starting the whole thing.
You can for instance run it with
--nuve
to only start nuve. For now, no further customization of the configuration is provided.For users of the older Dockerfile
This new Dockerfile is located in the root of the repository to be able to generate the context via
COPY
Also,
CMD
has been changed toENTRYPOINT
to make it easier to pass parameters to the init script. Remember you have to use--entrypoint
to change the entrypoint instead of just passing the script as a parameter.[] It needs and includes Unit Tests
Changes in Client or Server public APIs
Add a detailed description of any change in the public APIs.
[] It includes documentation for these changes in
/doc
.