You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Current distribution method on macOS rely on HomeBrew.
This distribution solution as a long history of vulnerabilities, design weaknesses, poor respect of macOS development guidelines and is usually really slow to adopt new macOS major releases.
Plus, HomeBrew does not provide any scalable deployment method for a managed fleets.
macOS in enterprises are managed by MDM, even for developers, and the fleet management can be used to ensure toolbox consistency across developers endpoints. Which cannot be done with HomeBrew.
Describe the solution you'd like
Vapor, as any solution working on macOS, should provide official release as a standard pkg, ideally over a versioned release API such as the GitHub release system.
Such an evolution would allow update automation for all managed fleets (MDM via some fleet automation tools can download GH Releases and distribute them automatically).
As an optional method aside the direct pkg, it could be also great to support MacPorts, which is a more mature and robust port system for macOS.
Describe alternatives you've considered
Alternative would be for us to download the sources and generate our custom pkg each time. And handle the signature ourselves.
Additional context
Product adoption are also made via the help of the IT team that will deal with product distribution on a fleet. Helping them with state of the art distribution method will make them more prone to push Vapor in a discussion.
The text was updated successfully, but these errors were encountered:
I would also like to see this. I absolutely refuse to install HomeBrew on any machines that I manage. It writes all over the place and is not disciplined enough with respect to packages vulnerabilities to be safe. It is great for developers because anyone can produce a brew, but that is exactly the problem.
I would like to see the linux instructions adapted to macOS as an alternative.
Turns out if you have any reasonable MacPorts packages installed the Linux instructions seem to work fine. There are probably some dependency issues, but I did not have any problems.
Is your feature request related to a problem? Please describe.
Current distribution method on macOS rely on HomeBrew.
This distribution solution as a long history of vulnerabilities, design weaknesses, poor respect of macOS development guidelines and is usually really slow to adopt new macOS major releases.
Plus, HomeBrew does not provide any scalable deployment method for a managed fleets.
macOS in enterprises are managed by MDM, even for developers, and the fleet management can be used to ensure toolbox consistency across developers endpoints. Which cannot be done with HomeBrew.
Describe the solution you'd like
Vapor, as any solution working on macOS, should provide official release as a standard pkg, ideally over a versioned release API such as the GitHub release system.
Such an evolution would allow update automation for all managed fleets (MDM via some fleet automation tools can download GH Releases and distribute them automatically).
As an optional method aside the direct pkg, it could be also great to support MacPorts, which is a more mature and robust port system for macOS.
Describe alternatives you've considered
Alternative would be for us to download the sources and generate our custom pkg each time. And handle the signature ourselves.
Additional context
Product adoption are also made via the help of the IT team that will deal with product distribution on a fleet. Helping them with state of the art distribution method will make them more prone to push Vapor in a discussion.
The text was updated successfully, but these errors were encountered: