Consider using Equinox or other release tool

[willglynn]

Equinox handles a lot of open problems:

• Builds the binaries for many target platforms
• Creates installers appropriate for each target platform
• Combines the result into a pretty install page
• Makes it trivial to self-update after installation

See also the blog post announcing Equinox. It's free for open-source tools, and signing in with GitHub instantly gets you a sandbox account to try it out.

I have no particular connection to Equinox, and there are some other options in this space. I think FSM should use one of them.

[mroote]

I think it might be better to use a more general build tool such as Travis in order to get some CI features also.

[willglynn]

This would be complimentary to CI. Travis would handle making sure nothing broke during development (pushing commits and evaluating PRs), while Equinox would handle user-facing releases (downloads and updates).

[mroote]

I read a bit more about Equinox and I see what you mean. This could help deployment to users in the future if there are many new versions of the server manager. If someone has a deployed server updating may be easier for them.

Another option might be to make the application build in a Dockerfile and distribute the application through Docker Hub.