etcher/docs/PUBLISHING.md
Juan Cruz Viotti ef96ae86a0 chore: stop requiring a specific nodejs version to build Etcher (#584)
We were previously requiring users to run the exact same NodeJS version as
Electron bundled in order to avoid native add-on compilation incompatibilities,
however this problem is completely mitigated by configuring NPM to build
against an Electron specific V8.

Signed-off-by: Juan Cruz Viotti <jviottidc@gmail.com>
2016-07-19 22:28:41 -04:00

2.2 KiB

Publishing Etcher

This is a small guide to package and publish Etcher to all supported operating systems.

Common Pre-requisites

Signing

OS X

  1. Get our Apple Developer ID certificate for signing applications distributed outside the Mac App Store from the Resin.io Apple account.

  2. Install the Developer ID certificate to your Mac's Keychain by double clicking on the certificate file.

The application will be signed automatically using this certificate when packaging for OS X.

Windows

  1. Get access to our code signing certificate and decryption key as a Resin.io employee by asking for it to the relevant people.

  2. Place the certificate in the root of the Etcher repository naming it certificate.p12.

Packaging

The resulting installers will be saved to etcher-release/installers.

Windows

Pre-requisites:

Run the following command from the Developer Command Prompt for VS2013, to ensure all Visual Studio command utilities are available in the %PATH%:

> .\scripts\build\windows.bat all <x64|x86>

OS X

Pre-requisites:

Run the following command:

$ ./scripts/build/darwin.sh all

GNU/Linux

Run the following command:

$ ./scripts/build/linux.sh all <x64|x86>

Publishing

Make sure you have the AWS CLI tool installed and configured to access Resin.io's production downloads S3 bucket.

The publishing script only runs on UNIX based operating systems for now. You can use something like Cygwin to run it on Windows.

Run the following command:

./scripts/publish.sh <file>