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
Dockerise release-it for executing without node runtime #1045
Comments
I haven't considered that before, because I'm not a Docker expert. But I'm willing to include it, since it should be low maintenance (someone added a Dockerfile in another project which went well). |
Cool! I have an idea to manage additional dependencies besides the required one, and then we can go from there, I will try to get some time on it relatively soon :) |
I am putting my thoughts as I finally got some time to work on it.
The problem... Git!
Still working out the git part, but the rest was quite straightforward. |
Hey @webpro I finished the dockerised version. Tested internally in my projects, I made some decisions for GPG, SSH and GIT. I tested into multiple conditions and more to come, but so far all working :) |
Very cool! Sorry I didn't respond before. Thanks a lot for the updates, here's looking forward to the final version :) |
All good! Fun weekend ahead for me :) |
So.. I finished https://github.com/juancarlosjr97/release-it-containerized. My main drive for this was for project that do not run with node and do not need to have any configuration around it, and I would dare to say that I have done it! All done thanks to the amazing work of release-it that inspired me :) |
Guess we can close this one now, it's linked to from the docs here: https://github.com/release-it/release-it#containerized Thanks for all the help and release-it-containerized! |
Hello,
I was wondering if you have considered Dockerise the project to run the release and publish a docker version of it that just executes and that is it.
If not, and the idea sounds good, I am happy to contribute and raise the first MRs with some thoughts around it.
The text was updated successfully, but these errors were encountered: