-
Notifications
You must be signed in to change notification settings - Fork 50
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
create both deb and rpm files when releasing #901
Conversation
Great work!
A thought: it might be good to run Conduit as a |
@hariso true! but it's up to the user tbh, we can suggest that way in the |
@maha-hajja That certainly is an option. I'm under impression that Conduit would be something that would run as a service. Otherwise, it makes the Debian package almost no different than running the Conduit binary. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@maha-hajja I see that the created filenames contain the suffix _linux_386
, _linux_amd64
and _linux_arm64
. Is it possible to rename those to _Linux_i386
, _Linux_x86_64
and _Linux_arm64
respectively? This way we would keep the naming consistent with the other assets that are produced in a release.
Good callout for the names! 👍 It maybe even makes sense to drop |
I would leave |
@lovromazgon done! added a name template for nfpms, tested on https://github.com/ConduitIO/conduit-maha/releases/tag/v0.5.1 |
Description
reference to nfpm: https://nfpm.goreleaser.com/configuration/
tested on a conduit fork https://github.com/ConduitIO/conduit-maha/releases/tag/v0.3.0
you can test installing it using docker:
Related to #824
Quick checks: