Create installable packages

[ezeoleaf]

Is your feature request related to a problem? Please describe.
Yes. People do need to have go install to build/install the bot.

Describe the solution you'd like
Try to publish the executables to brew, apt-get and other solutions

Describe alternatives you've considered
Have the executables in S3 or somewhere

[till]

Would you be up for a goreleaser based chain with nfpm?

[ezeoleaf]

@till Yes, I think we can start with that, go ahead :D

[till]

@ezeoleaf I would probably add a workflow to do all the releasing? Not entirely sure how to do changelogs. I have a configuration almost ready so you can have a look.

[till]

Speaking of s3, I haven't use it yet, but cloudsmith offers free repositories for OSS? Thoughts?

[till]

Speaking of s3, I haven't use it yet, but cloudsmith offers free repositories for OSS? Thoughts?

So this looks easy enough.
https://github.com/cloudsmith-io/action

With the workflow that I added, in theory, you could get away with a git tag -a vABC and then it would create a github release and publish larry there. And then in another step, it could use the the action and push Alpine, Debian and RH packages to a Cloudsmith repository.

Reason why I suggest this vs. a bare repositories is that I am not sure if there is anything that's "good" (easy) to handle multiple repositories. Last time I checked, all the tooling still works like in the 90s. 😂

[ezeoleaf]

@till Yes, I think we can go with that approach and try from there :D

[till]

Do you want to sign up and add the secret? I can create the rest.

[ezeoleaf]

@till The secret is added in the repo under this env CLOUDSMITH_API_KEY