-
Notifications
You must be signed in to change notification settings - Fork 105
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
provide more release binaries with release-please and goreleaser #96
Comments
I will look into rpm support. Goreleaser looks interesting. Switching build systems requires a lot of manual work from my side to verify things are working, which usually involves bringing up VMs, installing and verifying, etc. |
I'm working on a repo that investigates all this with a baseline wails app. Using devbox, instead of pure nix. One challenge is that within a custom goreleaser Docker image where I've installed devbox and thus presumably all the required deps:
🤌😬 |
I would also kindly ask to include a portable Windows release, which stores the config in the current directory and does not write to the Windows registry. |
@ags1234 have you tried the windows cli binary? it could be used in a portable way (you just need to keep the binary in the same folder as the paisa.yaml) |
@ananthakumaran Oh, thanks! I was deterred to try the CLI version because I thought it does not have a GUI. However, it seems it has a web UI. And it looks great. You did a great job with Paisa! |
I'm on fedora, so non of the desktop release binaries work for me and i dont want to run it as a webserver.
if you use this goreleaser docker image with release-please then you can get rid of most your custom bespoke build workflows and easily provide everyone with all kinds of binary formats.
it'll also take care of building, publishing:
The text was updated successfully, but these errors were encountered: