should the master image be the base image

[roovo]

It seems cleaner to me to tag the base image (form which other project images are built) as "base" rather than "master".

With the current system:

#             REPOSITORY          TAG                ....
#             test                master.093e707     ....
#             test                master             ....

On the last line, master just means the base image (as it could actually be a non-master git branch) but it means the git branch master in the line above. If it's called base it'd look like:

REPOSITORY          TAG                ....
test                master.093e707     ....
test                base               ....

which feels more intuitive and intent revealing. Happy to add a pull request if it makes sense to you too.

Cheers

Roovo

[gerhard]

The reason why I've went with master is because it matches the state of a git repository. All application code is coming from git, so introducing base adds an extra mapping step. It does add indirection, yes, but is it valuable enough? I've expanded on my approach at the most recent London Docker Meetup, slides are already up, blog post will follow shortly.

As for dockerize, I've captured all the knowledge in an Ansible playbook. I regard that as the next evolution of the dockerize concept.

Thanks for weighing in on this 👍

[robodude666]

By "... Ansible Playbook. ... evolution of the dockerize concept" are you referring to your ansible-docker project?

[gerhard]

Yes, pretty much. I've done a lot more progress since, will be updating the repo when I wrap up the second phase.