Open larrycai opened 9 years ago
Releasing the binary is convenient for developers to use it without installing go
or `docker. But each binary is platform related and we should compile for x86 and amd64 for both linux and mac os. The total size of these binaries is unacceptable and we always put them in another repository, just like run-release.
I think docker is the nice way to package the application. Are you using pirate
in the machine which doesn't install docker
?
no, I always use docker to wrap it. we are #Dockerfile联盟# ;-)
just think to release docker image with pirate binary which is only x86
On Tue, Jan 27, 2015 at 9:19 AM, tobe notifications@github.com wrote:
Releasing the binary is convenient for developers to use it without installing go or `docker. But each binary is platform related and we should compile for x86 and amd64 for both linux and mac os. The total size of these binaries is unacceptable and we always put them in another repository, just like run-release https://github.com/runscripts/run-release.
I think docker is the nice way to package the application. Are you using pirate in the machine which doesn't install docker?
— Reply to this email directly or view it on GitHub https://github.com/tobegit3hub/pirate/issues/38#issuecomment-71573358.
True software development embraces consistent inconsistency. blog: http://larrycaiyu.com/blog (en), http://larrycaiyu.com (chinese)
Maybe do it in other repo. It's not really compatible for us and no need to add it in docker image :smiley:
if we set drone.io for CI build to generate pirate binary file, it could be good to have a pure binary release, then it shall decrease the images.
Shall we do it ?