dockerfile for the app - image works with openshift/kubernetes too

[sfarosu]

Created this dockerfile for passwordpusher app. It works with docker/openshift/kubernetes too. I could also work on an openshift template to create all the objects + persistent storage if there's no support in the app for mysql.

Image available here: https://hub.docker.com/r/sfarosu/passwordpusher/

[pglombardo]

Great stuff @sfarosu. If we set RAILS_ENV=production and configure config/database.yml, we could make the production environment support/run mysql or postgresql out of the box. (Support exists, it just needs to be configured)

In the Dockerfile, the would then be:

ENV=RAILS_ENV=production
ENTRYPOINT [ "bundle", "exec", "foreman", "start", "web" ]

But could a single Docker image also run postgres or would that have to be broken out into a separate image?

[sfarosu]

To be honest i think we should concentrate on the real deal, Openshift and Kubernetes. Don't think there are many people running the app manually. But still in this case i would see a docker compose with 2 containers, one i've built + one with mysql or whatever and it's data (volume) would be saved on the host machine in a folder so it survives container recreation not only restarts.

On the other hand making a nice openshift template with deployments would be more attractive, with one simple command you could run the whole thing.

In any case, let's do both, so if you can prepare config/database.yml for mysql i'll start working on docker compose.

[pglombardo]

Good points - I agree. And actually, if we set an ENV var of DATABASE_URL, it can point to any remote database and it overrides the config/database.yaml automatically . Much easier/simpler.

e.g.

DATABASE_URL=postgresql://user:pw@host:5432/db
DATABASE_URL=mysql://user:pw@host:5432/db

I'll merge and update the docs/README separately. (unless you want to do this by all means...)
I'll add a separate issue to add an Openshift template.

Thanks for the help!