You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 24, 2021. It is now read-only.
Currently make artifact-linux-x86_64 will build the atrifact on the host machine. IMO we should build it via docker container (can do with a shared volume or copy from the build container).
Pros - good idea - I actually used both techniques.
shared volume is easier (but you still have a host), copy from container is cleaner but you need to save the container id (you get it from the run command), can be annoying to write it when you develop in Java since build is long but in Go is the prefered way IMO.
Cons - lets say we move our project to github actions for example so we can build in mac and windows, if we build in docker we won't be able to leverage the platforms for the different builds
Cons - lets say we move our project to github actions for example so we can build in mac and windows, if we build in docker we won't be able to leverage the platforms for the different builds
Agree. However the compatibility problem is very linux specific
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently
make artifact-linux-x86_64
will build the atrifact on the host machine. IMO we should build it via docker container (can do with a shared volume or copy from the build container).@yonidavidson WDYT?
The text was updated successfully, but these errors were encountered: