Traditionally software installs for servers use a package manager, or at least have an updated file that simply says "latest" in the name instead of the version number.
To make deployments much easier, I highly recommend having at least a file named similarly to remote-syslog2_latest_amd64.deb. When you've gotten to 1.X, to prevent breaking systems, remote-syslog2_latest_1.x_amd64.deb or the like would be much appreciated.
In the mean time, is there any file like that or some way to keep things up to date with bug fixes and the like?
Taking it a step further and providing an Apt repo will allow us to keep our software updated without having to implement a cron job. Canonical's Launchpad might be a smart move for Papertrail to keep the overhead low on these releases.
Traditionally software installs for servers use a package manager, or at least have an updated file that simply says "latest" in the name instead of the version number.
To make deployments much easier, I highly recommend having at least a file named similarly to
remote-syslog2_latest_amd64.deb. When you've gotten to 1.X, to prevent breaking systems,remote-syslog2_latest_1.x_amd64.debor the like would be much appreciated.In the mean time, is there any file like that or some way to keep things up to date with bug fixes and the like?
Taking it a step further and providing an Apt repo will allow us to keep our software updated without having to implement a cron job. Canonical's Launchpad might be a smart move for Papertrail to keep the overhead low on these releases.