Windows, deb, rpm, brew installers

[badgerwithagun]

Orko currently requires manual installation and can be sensitive to JRE versions, amongst other things. We need to produce proper installers for standalone deployment.

https://stackoverflow.com/questions/1378129/how-to-create-installers-with-maven

DEBs and RPMs should ideally be deployed to a suitable repo so they can be managed with apt etc.

Should deploy these artifacts to the GitHub release when doing a tag build.

A re-usable configurator application to allow a user to set up their exchange API keys would be nice too.

[badgerwithagun]

I have had good experiences with Tanuki Wrapper: https://wrapper.tanukisoftware.com/doc/english/introduction.html

That makes the installer bit the simple bit.

[kenibarwick]

For my benefit later

https://nsis.sourceforge.io/Simple_tutorials

[kenibarwick]

• (a) make sure/get installed a JRE
• (b) Wrap the JAR as a window service so it runs on startup
• (c) register the windows service
• (d) provide a means to set up all the config settings

[badgerwithagun]

On Linux installs, it strikes me that there is a "right" way and a "wrong" way to go about this. The "right" way is that all the application's dependencies also are installed using the platform's package manager, so they exist as shared dependencies (https://wiki.debian.org/Java/MavenDebianHelper).

The "wrong" way is to bundle everything together along with a JRE and deploy that.

In the middle is to at least make sure that obvious prerequisites like the JRE are installed separately and bundle all the Java together.