Add a package builder that generates installers for Win, Mac and Linux

[flyingzumwalt]

Everyday users want to use a native OS installer to install apps. In order to support this, we need to use a package builder like electron-builder to generate those installers.

What to do:

• Add an electron package builder like electron-builder that gan generate installers for Windows, Mac and Linux
• Configure the builder so we can automatically generate new installers and release them to dist.ipfs.io

There's some helpful, but slightly outdated, info in #20.

Related Issues: closes #16, closes #20

[daviddias]

This is now possible thanks to the work @thisconnect did on js-ipfsd-ctl. @hacdias does this sound like something you can tackle as well? You can find docs on packaging left by @thisconnect here: https://github.com/ipfs/js-ipfsd-ctl#packaging

[hacdias]

So, this is related to #512. Dear CI master @victorbjelkholm, the command to build the distributables is:

./node_modules/.bin/electron-forge package --arch=ia32,x64 --platform=win32,linux,darwin

You just need to change the arch and platform flags to build for the desired platforms and arches. The output will be saved on:

./out/{package_type}/{arch}/files_are_here

If it simplifies your life, there is the publish command you can use: https://electronforge.io/cli/publish.

Hope it helps!

[victorb]

@hacdias started working on this here: #514 still a work in progress.

[hacdias]

Let's just leave this opened until Packaging is fully working.

[hacdias]

Sooooo! Since @diasdavid merged #514, Jenkins is actually building the right stuff! And the binary for Windows is running flawlessly and I'm very happy with it!!! Thanks @victorbjelkholm!!!

Although, there is this "problem" on Windows:

We have to sign it somehow as it is stated here so the publisher is recognized and this message doesn't prompt out.

On Ubuntu/Mint this problem persists.

[victorb]

@hacdias woah! That's great news! Hm, signing will be a bit trickier to solve right now, as we don't have secrets-management in jenkins yet but it's planned already because we have other builds that will need it as well.

I think this same problem happens in macOS (you'll need to right-click and then click open instead of double-click, otherwise you get a similar dialog) so maybe not a blocker for now.

[hacdias]

@victorbjelkholm okay then. Soooo, the only problem are the Linux builds! Those don't add an icon nor anything to the path. I'll try to figure out why.