-
-
Notifications
You must be signed in to change notification settings - Fork 53
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
Native packaging and updating #219
Comments
Doesn’t go produce self contain static binaries which can be simply downloaded from anywhere and ran on the target platform? |
Yes it does . I am explaining a way to make it easier for devs and users to install compose-process. https://github.com/F1bonacc1/process-compose/releases/tag/v1.18.0 Is zips and tars etc . If it was not compressed then that’s easier for installs. I guess you use go released at the moment ? then you hydrapp, which does full packaging . |
My ask is that you initially make go released also output binaries without zip , etc . The current mechanism is then unaffected. should be a small change to go released . then if your interested can use Trapp to make dmg and msi ,but only if you interested . |
imho as i recall best installers for windows for powerusers (assuming PC is for power users anyway) are scoop (fully OSS and git centric) and winget (official from MS) (chocolatey is dead, appx seems not the way for cli/tui tools imho) |
Feature Request
More user friendly way to install apps for users.
This is especially acute for Windows users that tend to be less tech savvy.
Use Case:
I have a class of users that are not technical and need to run binaries from the dev team.
These tend to work in the a Team but are not coders. SO they need a way to really easily install and run process-compose.
Proposed Change:
https://github.com/pojntfx/hydrapp is what I currently use for golang project packaging and installing and updating. It works natively without any other things needing to be installed on Windows, Mac and Linux.
Hydrapp can install anything.
I have been using it for many golang projects where I need users to be able to easily install, and devs to not have to spent ages on packaging.
Who Benefits From The Change(s)?
Devs and non devs.
The existing CURL based system is still present for devs to use locally and on servers or in their docker containers.
Alternative Approaches
There are not many golang packaging systems like this. Its pretty nice.
The text was updated successfully, but these errors were encountered: