3 ms·
Because then you also need to host a feed, and keep it updated when new releases become available, and keep it updated when new plugin releases become available
by jsmeaton 10y ago
Because then you also need to host a feed, and keep it updated when new releases become available, and keep it updated when new plugin releases become available, and ensure the feed stays up, and maintain patches, and maintain required dependencies. All the things that package maintainers (thank you!) do for the ecosystem. Unless there's substantial gain why not just stick with Nginx?
For what it's worth though FPM is awesome, and has made my life better a number of times. If you have to have software that isn't packaged and you aren't familiar with packaging, look into FPM.
https://github.com/jordansissel/fpm https://github.com/jordansissel/fpm
- jamespo 10y agoWhat dependencies? This is statically compiled go. Binaries are available, automating a download and wrapping into a package with FPM is not that much effort.
- jsmeaton 10y agoRight, it's not a tonne of work if you need it or really want it. But it's still extra effort to move away from a supported package provided by the package management software. Not providing repos means you lose the users who might want to play around with it but don't have any packaging experience. This shouldn't be very controversial.