Feature request: snap package

Description

It may be good to consider making a snap of Buffalo and publishing it to the snap store for Linux users.

Some benefits:

• Users could easily install it via snap install buffalo
• The app can be discovered easily via snap find or via the snapcraft website [1].
• Package will be kept up to date automatically whenever the buffalo developers release a new version.
• Builds can be automated via, build.snapcraft.io, travis, or launchpad. If configured, every commit which lands in master will trigger a new build directly to the store automatically for all supported architectures.
• Rollback: if something goes wrong in an update, users can roll back to a previous release easily and keep their config/data
• Channels: You can have multiple versions of Buffalo active in the store. Users choose level of risk by selecting a channel. If you're doing a beta testing session, put the beta release in that channel and testers can snap install buffalo --beta to get the new goodness, then switch to stable when the beta is over.
• Tracks: You can support multiple stable releases in the store. So you could have the 0.1 branch in one track and 0.2 in another. You can publish updates to both, separately and have some users on each. Users who want to be 'sticky' on 0.1 can stay there. Very useful if 0.x is a breaking release, as it allows people to stay on existing version, and continue to get updates (if you push them).
• Metrics: The store provides aggregated details about how many people are running each release, and geographic location. This might be useful for you to focus development effort, translation drives etc.

There is a forum [3] where you can get help when making the snapcraft configuration file.

[1] http://snapcraft.io/ [2] https://snapcraft.io/docs/core/install [3] http://forum.snapcraft.io/