-
Notifications
You must be signed in to change notification settings - Fork 17
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
Docker image #56
Comments
Thanks for your feedback @micdenny ! It looks like we have one project publishing to dockerhub, but it doesn't seem particularly widespread amongst our open source projects - and the one project which does hasn't been re-published in a while. I'll ask around internally to figure out what we can do here. At the very least I imagine it would be helpful to produce some form of easy to run release artifacts. |
Usually a regularly updated docker image is very useful also to test locally, then of course for containerized production environment. Personally I will use it to deeply test configurations locally before pushing it on production, in fact I've already did an image locally by pushing the artifacts that are produced from your well documented docker build process, the next step will be to have an automation to take those artifacts and create an image and push to the gallery, with a proper readme and so on. Now my image is done by an easy ugly Dockerfile as this: FROM ubuntu:latest
COPY amqpprox* /usr/local/bin
CMD [ "amqpprox" ] That sits inside the bin folder Told this if we can also push an artifacts on a public linux package repository would be great for non-containerized environment, but I don't have any experience on that. |
Any update on this? |
Would be very nice to have a docker image hosted on the hub ready to be configured and run, with a build pipeline that is connected to this repo and builds a new version every time there's a new tagged version.
The text was updated successfully, but these errors were encountered: