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
Some suggestions and an alternative to Dockertest #35
Comments
Another small detail, rather than randomly picking a port with a PRNG, it can let Docker do it for you (which means there is no risk of collisions). |
Hey looks cool! I like your idea of using docker compose to set up the environment. Really merges "production" and "testing" stages. How do you get a container instance? Didn't find it in the tests / docs. Also would go-compose work with go-dockerclient as suggested in #11 ? |
The Compose type has a Containers map in it, keys are container names, and IIUC go-dockerclient doesn't support docker compose, which is why I didn't On Mon, Mar 14, 2016 at 2:38 PM, Aeneas notifications@github.com wrote:
|
@sbani will take a look at this :) |
this will work with #46 |
Hi Aeneas, I'm opening an issue in absence of other ways to contact you :) I just wanted to let you know I have been working on an alternative approach to achieve the same function of this library, and published it at: https://github.com/ibrt/go-compose. I believe this approach is simpler and has few advantages (listed below), maybe it could be interesting for you to have a look and possibly borrow some ideas!
On the downside, it doesn't have any support for standard or predefined services. I am planning to add them in separate subpackages, so callers can actually import only the dependencies they need.
Best,
Ivan
The text was updated successfully, but these errors were encountered: