Github user klaemo commented on the pull request:
https://github.com/apache/couchdb/pull/340#issuecomment-136390637
It's possible, but I think that involves cloning the couchdb repo once more
inside of the container.
Essentially, there are two ways I can think of:
1. Have the Dockerfile along side the src, `COPY` the (already cloned) src
into the container and build that beast. It pretty much acts like a Makefile.
In that case having the Dockerfile in a different repo wouldn't make much
sense. The upside is cloning the repo only once and being aware of local
changes the developer might have made.
2. Pull in the Dockerfile from `couchdb-docker`, clone the repo inside of
the container and build. Downside: having to clone twice and it doesn't take
local src changes into account because it always pulls from the remote (that's
how https://github.com/klaemo/docker-couchdb/tree/master/2.0-dev works atm)
A combination of 1 and 2 is possible, but it seems weird to have the
Dockerfile in a different repo if it depends on the source code being there.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
