-
Notifications
You must be signed in to change notification settings - Fork 57
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 with go-enum #171
Comments
Sounds like a reasonable request... I'll see what I can do |
Just as an example (it can be helpful to you) |
@abice Any news on it? |
Haven't had time to work on it, sorry! |
Oh... I'm waiting for it very much :( |
Same for me! I can contribute if necessary, @abice. Just give me a shout. 😌 |
This is not working yet... still working out the bugs 😄 sorry! And just for everyone's information, apparently despite the fact that I imported the goimports tool, it actually makes a call to the go binary for at least getting the go environment information. I'm not sure how I want to get around this at the moment, and will take a sec to figure that out. Sorry about getting your hopes up 😞 |
Alright, so I'm going to leave this ticket open as a reminder that I need to figure out how to run the go-enum binary without the go binary installed (or at least a smaller image to do so)... but for now, you can use the image I've updated some of my makefiles to look like this, and they successfully generate the enums correctly.
If anyone has an idea of how to get the go-enum binary to do the goimports functionality without executing a go binary, I'm open to suggestions! |
Could you please provide an "official" multi-arch docker image to use this tool? It can be simply deployed to the ghcr.io, for example. Use case - a more simple installation in the docker context, like:
COPY --from=abice/go-enum:v0.5.5 /usr/local/bin/go-enum /bin/go-enum
If you need help with it, I can make a PR with the required changes.
The text was updated successfully, but these errors were encountered: