Add Dockerfile and release pipeline

[derberg]

• example Dockerfile that we already have for the Generator CLI -> https://github.com/asyncapi/generator/blob/master/Dockerfile
• but instead of installing npm package, and using CLI from npm, we can actually build even smaller image, not based on node alpine. We would just plug into https://github.com/asyncapi/cli/blob/master/.github/workflows/upload-release-assets.yml workflow where we generate different distro versions, including Linux, and use linux binary in docker? Just an idea 🤷🏼
• make sure it is plugged into the release flow. Example -> https://github.com/asyncapi/generator/blob/master/.github/workflows/release-docker.yml

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 120 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. AsyncAPI Initiative is a Linux Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️

[derberg]

we still need docker

[thulieblack]

This issue is part of the AsyncAPI Bounty Program, interested contributors need to follow the guidelines below to ensure fairness and timely completion of assigned tasks:

Task Assignment

The assignment of tasks will be prioritized in the following order:

• AsyncAPI maintainers (from any repository)
• Regular contributors (individuals who have merged three or more pull requests)
• Other (if an individual doesn't fall under the above, the maintainer can determine the criteria i.e regular volunteers, etc)

We encouraged everyone to apply as long as the task is for you (falls under your skill set). We will not be using the first comment - get assigned method for assignments. Instead, we will provide 3 days to consider all individuals interested before assigning any bounty task.

Deadline

To maintain accountability and ensure the timely completion of the deadline for this task will be 4- 6 weeks from the date of assignment. If a contributor requires an extension on their task, it should be communicated and approved by the maintainer.

Issue Tracking and Updates

Contributors must provide weekly updates on the task they are working on to help maintainers stay informed of progress. If a contributor fails to provide an update, they will be reminded via a ping. If a contributor fails to provide an update after three pings over three weeks, we will assume they have silently dropped the issue, and it will be reassigned to someone else.

Issue Drop-outs

Any contributor who drops an assigned issue will be penalized and will not be eligible to participate in the bounty program for 6 months. We understand that unforeseen circumstances can arise, and dropping an assigned issue may be unavoidable in some cases. However, we believe that enforcing this penalty is necessary to ensure the effectiveness of the bounty program, respect maintainer time, and honor the efforts of other contributors who could have solved the issue but were unable to do so due to the drop-out.

We encourage all contributors to follow these guidelines to ensure a fair and timely completion of tasks assigned through our bounty program.

[mediba123]

I would recommend adding examples to the "Add Dockerfile and release pipeline #358" issue to provide more clarity for developers who are not familiar with Dockerfiles or release pipelines.

For the Dockerfile, an example could be provided that shows how to set up a basic Dockerfile with the necessary dependencies and instructions to run the application. Additionally, it may be helpful to provide a sample Docker Compose file that can be used to build and run the Docker image.

For the release pipeline, an example could be given that demonstrates how to set up a basic pipeline using a popular CI/CD tool such as Jenkins or GitLab CI. This could include steps for building the Docker image, running tests, and deploying the application to a staging or production environment.

By providing these examples, developers can have a better understanding of how to use Docker and release pipelines within the context of the project, which can help them to more quickly and effectively contribute to the codebase.

[Savio629]

I would like to give this issue a try!

[derberg]

@mediba123 thanks for the hints. Just keep in mind this is not a good first issue for first timers. This is a bounty issue that we pay for to be completed. This requires assignee to do some more work on their own.

@Savio629 please go ahead and lemme know if you need some help

[derberg]

@Savio629 here you have a video of me explaining what has to be done. Some copy/pasting and some docs, and some local testing to make sure docs are actually accurate 😄

https://www.youtube.com/watch?v=aJgHM7D5NPw

[Savio629]

Thank you so much @derberg 🍻
I'll look into it a day or so.
Once again, thank you so much for your assistance💜

[mediba123]

I hope one day I find a mentor or opportunity to contribute, thank you.

[thulieblack]

@mediba123 we have the mentorship program coming up also the community is very open to help you. Let me know what you need to get started

[mediba123]

i would love if i find a link to that, because am ready to get started.

[mhmohona]

Hello @mediba123 , here is the link for AsyncAPI mentorship program - https://github.com/orgs/asyncapi/discussions/689

[derberg]

@Savio629 please specify if you will work on this one

[Savio629]

Yeah I'll work on this issue

[thulieblack]

@Savio629 when can we expect you to start working on the issue??

[Savio629]

Yeah I'll work on this issue

Actually I meant I'm working on the issue
My exams are going on right now so probably by the start of next week, I'll give an update on my progress.

[asyncapi-bot]

🎉 This issue has been resolved in version 0.47.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[derberg]

@Savio629 congrats! docker is published successfully https://hub.docker.com/repository/docker/asyncapi/cli/general 🚀 and docs are here https://www.asyncapi.com/docs/tools/cli/installation#docker

The only problem is that description update failed -> https://github.com/asyncapi/cli/actions/runs/5153139175/jobs/9280007038

It is because you configured it to grab description from GitHub which is too long in our case, so solve it by providing custom description inside the GH action. Please followup with another PR, can be chore type imho. I'll be out but @Souvikns will be here to review

@thulieblack another bounty issue completed 🚀

[Savio629]

Thank you so much Lukasz for your support.
I'll look into the problem and communicate with Souvikns....

[thulieblack]

Hey, @Savio629, congratulations on completing your issue.

This is how'll claim your bounty:

1. Go to AsyncAPI Open Collective page
2. Submit an expense and add details for the bounty issue
   
3. Voila! You get your coins🤑 !!