Installable via OS package managers

[bacongobbler]

As a user, I'd love to install the spin CLI similar to how I'd install other packages on Linux - through apt.

Something similar to

$ curl -fsSL https://apt.releases.fermyon.dev/gpg | sudo apt-key add -
$ sudo apt-add-repository "deb [arch=amd64] https://apt.releases.fermyon.dev $(lsb_release -cs) main"
$ sudo apt-get update && sudo apt-get install spin

(note: this is a very similar experience for HashiCorp's installation instructions for nomad, consul, vault, etc.)

[radu-matei]

I'd expand the scope of this and suggest we look at supporting package managers for macOS and Window as well.

[neodon]

I look for any kind of managed way to install something before sighing and running an installer script. Having only this option could be a deterrent for some types of devs to try out Fermyon. I realize it's a lot more work to define and generate other installation methods, however, so I understand if it's not time for this just yet.

Also, I'll just mention Homebrew on Linux here since it doesn't seem well-known. Or people automatically treat it as heretical without learning more. I've been using it for a few years and it's been pretty awesome, especially when I want to match up versions of software on my Mac and Linux PC. It uses the same package sources for both, so it would provide an option to release often on both--if you can get people to try it.

[radu-matei]

Hi, @neodon, thanks for the comment!
I agree, which is why I think this issue is something we want to prioritize really soon.
Particularly for the default package managers on Debian, macOS and Windows.

[kate-goldenring]

The spin software validation tool has claimed the spin package name in many OS package managers (brew , apt , chocolatey at minimum).

It seems like we may want to prioritize brew, apt, and chocolatey, for all of which spin is taken.

Wanted to kick off some brainstorming on alternative package names:

• fermyon-spin
• spin-up

Also, for brew, I am not familiar with how difficult it is to create a bottle that can be directly installed with brew install vs creating a fermyon tap that needs to be installed first. I am assuming creating a fermyon tap is easier, creating an installation experience similar to Nomad's.

[bacongobbler]

IIRC Homebrew does allow taps to be namespaced such that you can do a brew install fermyon/spin. This requires you to maintain your own tap.

https://github.com/Homebrew/brew/blob/master/docs/Taps.md

This is what we did for Draft: https://github.com/Azure/homebrew-draft

But yeah, rather unfortunate that we can't namespace the package for apt or chocolatey...

In cases where a name conflict arises and concepts like namespacing does not exist, I think fermyon-spin would be most appropriate. It would match a "namespaced" pattern where the company name comes before the package name.

[bacongobbler]

Found this while browsing how to create DEB packages: https://www.makeuseof.com/create-deb-packages-debian-ubuntu/

[ThorstenHans]

Any thoughts or any process regarding publishing a Fermyon PPA (Personal Package Archive)?