Add homebrew formulae

[abhi3700]

Description

This PR is to add Homebrew formulae for pulsar, facilitating easy installation on macOS.

As the installation can be done based on the formulae pulsar.rb code on main branch, so I tested via pushing the PR's code to another dummy repo.

Tested OK ✅

With this PR, this issue can be resolved.

[nazar-pc]

I'm a bit confused, do you expect this to still be a separate repo? I expected this to be submitted to the Pulsar itself.

[abhi3700]

@nazar-pc

I'm a bit confused, do you expect this to still be a separate repo? I expected this to be submitted to the Pulsar itself.

The intent is to make the pulsar.rb file hosted somewhere (as repo) & keep user away from downloading the entire pulsar repo so as to make the process look simple.

Not saying we can't do with pulsar repo though.

Let me know your thoughts.

[nazar-pc]

I see, what about an automation that would push a commit to a gh-pages branch after new macOS build of Pulsar is out? That way we don't need to update it manually ever again and GitHub Pages will take care of hosting it and avoid downloading the whole repo (that is assuming "static website" is a supported way in homebrew).

[abhi3700]

I see, what about an automation that would push a commit to a gh-pages branch after new macOS build of Pulsar is out? That way we don't need to update it manually ever again and GitHub Pages will take care of hosting it and avoid downloading the whole repo (that is assuming "static website" is a supported way in homebrew).

I was thinking for a while & also confirmed with @DaMandal0rian:

• Homebrew doesn't support static gh-page.
• Homebrew should be hosted on a separate repo as done here.

Putting here @DaMandal0rian's plan:

"Basically, I would trigger a job when new pulsar release is out, it dispatches the tag and sha to the homebrew repo, homebrew repo has an action to build the new formulae, and then a PR is opened by that action, then enable auto merge on the action so PRs are merged automatically if requirement checks pass. Alternatively, there is an action that does this without needing to dispatch data and will shorten the process.
https://github.com/marketplace/actions/bump-homebrew-formula "

I will let @DaMandal0rian take over from here.

[nazar-pc]

"Basically, I would trigger a job when new pulsar release is out, it dispatches the tag and sha to the homebrew repo, homebrew repo has an action to build the new formulae, and then a PR is opened by that action, then enable auto merge on the action so PRs are merged automatically if requirement checks pass. Alternatively, there is an action that does this without needing to dispatch data and will shorten the process.
https://github.com/marketplace/actions/bump-homebrew-formula "

I like this plan!

[abhi3700]

@nazar-pc
Can we merge this PR for the current release 0.7.4?

I will open an issue with @DaMandal0rian's plan, which can be submitted as another PR.

[nazar-pc]

Since we are keeping this repo, yes. Thanks for doing this!

[DaMandal0rian]

@abhi3700 I think you tagged the wrong person 😆