-
Notifications
You must be signed in to change notification settings - Fork 5
Conversation
@@ -1,17 +1,11 @@ | |||
up: | |||
up: build |
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.
Why is build
included here?
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've included build
so that make up
will always launch the latest version of the code. It might be confusing if someone does a git pull
and make up
but the container does not get updated
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.
👌
@@ -1,8 +1,12 @@ | |||
FROM moexmen/node:8 |
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.
Do we need to use any functionality specific to moexmen/node
?
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.
not really, any node 8 will do
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.
Nope, but moexmen/node
has some standardization across all the docker images that we are using. Such as timezone configuration and a WORKDIR
setting.
Coming to think of it, I'll make a change to copy the files to the /app
folder instead.
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.
oh I didn't now the name of the folder mattered.
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.
It didn't, but it's more of a standardization. So we know that if we enter a container built by us, we know that /app
folder will continue the application code.
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.
What do you think about using the base directory instead of /app
? It seems clearer and more obvious to me.
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.
What do you mean by base directory?
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 first directory you see when you enter the container.
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 yes. ADD . .
will work because the WORKDIR
is specified in the base image.
691aff2
to
0f752d1
Compare
README.md
Outdated
1. Clone this repository | ||
1. Copy sample env file `cp .env.example .env` | ||
1. Modify the env file with secrets `$EDITOR .env` | ||
1. Build image `make build` |
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.
If build
is included in up
, we don't need this step.
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.
Good call 👍
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.
We have a how to run on production doc in our internal repo also. When this is setup we should port the docker steps over too.
0f752d1
to
78a7731
Compare
78a7731
to
c302a5f
Compare
I've made some changes to the Docker setup.
.env
file to store per deployment configurationENTRYPOINT
instead ofCMD
(See Node v5.x.x does not exit on Ctrl-C in Docker container nodejs/node#4182)I've also updated the README.md file, and remove old files that are not necessary