electron-simple-publisher

Description

This module makes easy to publish updates created by electron-builder. Now SSH, github, ftp, Amazon S3 and local release transports are supported. You can enable update feature in your application using electron-simple-updater

Installation

Install with npm:

npm install --save-dev electron-simple-publisher

Usage

1. For windows build set the target value to squirrel in package.json:

...
"build": {
  ...
  "win": {
    "target": "squirrel"
  }
},
...

2. Make a distributive package using electron-builder

3. Set options: You can specify all option through command line arguments, but it's easier to store the config in publisher.js or publisher.json in the project root. Here is an example for publishing through SSH:

1{
2  "transport": {
3    "module": "ssh",
4    "host": "example.com",
5    "username": "user",
6    "password": "user's password",
7    "remotePath": "/www/example.com/updates",
8    "remoteUrl": "http://example.com/updates",
9  },
10  "fields": { // Additional fields which will be added to updates.json
11    "readme": "The first version"
12  },
13  // If you've already set package.json:updater.url you can skip this option:
14  "metaFileUrl": "http://example.com/updates/update.json",
15  // Builds contained these substrings will be ignored when run clean command
16  "except": [
17    "prod-v0.5.0"
18  ]
19}

4. Run a publish command:

$ node_modules/.bin/publish - will publish the latest build for the current platform

Command line arguments

1Usage: publish [command] [options] [arguments]
2
3Commands (default is publish):
4  publish [configFile] [buildId1 Id2 …|all] Publish a new build(s).
5  replace [configFile] [buildId]            Replace the current build.
6  remove  [configFile] [buildId1 Id2 …]     Remove one or more builds.
7  clean   [configFile]                      Remove builds missed in updates.json
8    -e, --except NAME1,NAME2                NAME1,NAME2 will be preserved
9  list    [configFile]                      Show builds on a hosting.
10
11BuildId has a following format: [platform]-[arch]-[channel]-[version]
12  You can specify only a part of buildId, like linux-x64, defaults:
13    platform: process.platform
14    arch:     process.arch
15    channel:  package.json:updater.channel or prod
16    version:  package.json:version
17
18Options:
19  configFile             File with json ext, defaults to ./publisher.js
20  -t, --transport        Selected transport
21      --transport.{name} Specify a transport option
22  -p, --path             Path to distributive files (default dist).
23  -d, --debug            Show debug information
24  -n, --noprogress       Don't show upload progress
25      --fields.{name}    Specify a field in the target updates.json file 
26      --help             Show this message
27      --version          Show publisher version

Transports

SSH

Upload releases using SSH protocol. This transport uses ssh2 internally so you can check its documentation for all transport options.

Github

Upload updates to github releases. You can use this transport even if you don't want to share your source code. For this purposes you just need to create a public repository which will store your releases.

FTP

Upload releases using FTP protocol. This transport uses node-ftp internally so you can check its documentation for all transport options.

Amazon S3

Upload releases to S3 storage.

Azure Blob storage

Local

This transport allows to create file structure which can be uploaded to a server manually.

Related

• electron-builder - A complete solution to package and build an Electron app
• electron-simple-updater - Simple way to enable update for the electron application

License

Licensed under MIT.