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
Current distribution method of Kitura CLI is based on homebrew or npm, booth solution with security issue, poor respect of the macOS file system, and 0 mass deployment capabilities.
Please, support distribution of standard macOS package for Kitura CLI using github release system. This will allow sysadmin to automatically distribute and keep Kitura CLI updated on a whole fleet using the well know autopkg/munki or autopkg/jamf setup.
If for some reasons, you can't comply with this request, consider as an alternative to publish Kitura CLI with MacPort instead or in addition to homebrew. MacPort has a more robust distribution design and is able to create pkg from an admin workstation to distribute on a fleet without having to install it on the fleet itself.
Or eventually do both, macOS pkg with github release and MacPort support, that would be the best option.
The text was updated successfully, but these errors were encountered:
@ygini I am updating the release process for the CLI in #62 - as part of that, the macOS binary (standalone executable) will now be attached to each GitHub release in a .tar.gz.
This is the source for the Homebrew formula but can also be manually installed. It could form the basis of a macOS pkg, but that's beyond the scope of the work I'm doing here.
If you feel motivated to build on #62 to generate a (signed or unsigned) pkg as another installation option, then you'd be most welcome to raise a PR.
Hello,
Current distribution method of Kitura CLI is based on homebrew or npm, booth solution with security issue, poor respect of the macOS file system, and 0 mass deployment capabilities.
Please, support distribution of standard macOS package for Kitura CLI using github release system. This will allow sysadmin to automatically distribute and keep Kitura CLI updated on a whole fleet using the well know autopkg/munki or autopkg/jamf setup.
If for some reasons, you can't comply with this request, consider as an alternative to publish Kitura CLI with MacPort instead or in addition to homebrew. MacPort has a more robust distribution design and is able to create pkg from an admin workstation to distribute on a fleet without having to install it on the fleet itself.
Or eventually do both, macOS pkg with github release and MacPort support, that would be the best option.
The text was updated successfully, but these errors were encountered: