c94d4efd18
* Script for beta config; unique data dir, in-app env/type display
To release a beta build, increment the version and add -beta-N to the
end, then go through all the standard release activities.
The prepare-build npm script then updates key bits of the package.json
to ensure that the beta build can be installed alongside a production
build. This includes a new name ('Signal Beta') and a different location
for application data.
Note: Beta builds can be installed alongside production builds.
As part of this, a couple new bits of data are shown across the app:
- Environment (development or test, not shown if production)
- App Instance (disabled in production; used for multiple accounts)
These are shown in:
- The window title - both environment and app instance. You can tell
beta builds because the app name, preceding these data bits, is
different.
- The about window - both environment and app instance. You can tell
beta builds from the version number.
- The header added to the debug log - just environment. The version
number will tell us if it's a beta build, and app instance isn't
helpful.
* Turn on single-window mode in non-production modes
Because it's really frightening when you see 'unable to read from db'
errors in the console.
* aply.sh: More instructions for initial setup and testing
* Gruntfile: Get consistent with use of package.json datas
* Linux: manually update desktop keys, since macros not available
65 lines
2 KiB
JavaScript
65 lines
2 KiB
JavaScript
const fs = require('fs');
|
|
const _ = require('lodash');
|
|
|
|
const packageJson = require('./package.json');
|
|
const version = packageJson.version;
|
|
const beta = /beta/;
|
|
|
|
// You might be wondering why this file is necessary. It comes down to our desire to allow
|
|
// side-by-side installation of production and beta builds. Electron-Builder uses
|
|
// top-level data from package.json for many things, like the executable name, the
|
|
// debian package name, the install directory under /opt on linux, etc. We tried
|
|
// adding the ${channel} macro to these values, but Electron-Builder didn't like that.
|
|
|
|
if (!beta.test(version)) {
|
|
return;
|
|
}
|
|
|
|
console.log('prepare_build: updating package.json for beta build');
|
|
|
|
// -------
|
|
|
|
const NAME_PATH = 'name';
|
|
const PRODUCTION_NAME = 'signal-desktop';
|
|
const BETA_NAME = 'signal-desktop-beta';
|
|
|
|
const PRODUCT_NAME_PATH = 'productName';
|
|
const PRODUCTION_PRODUCT_NAME = 'Signal';
|
|
const BETA_PRODUCT_NAME = 'Signal Beta';
|
|
|
|
const APP_ID_PATH = 'build.appId';
|
|
const PRODUCTION_APP_ID = 'org.whispersystems.signal-desktop';
|
|
const BETA_APP_ID = 'org.whispersystems.signal-desktop-beta';
|
|
|
|
const STARTUP_WM_CLASS_PATH = 'build.linux.desktop.StartupWMClass';
|
|
const PRODUCTION_STARTUP_WM_CLASS = 'Signal';
|
|
const BETA_STARTUP_WM_CLASS = 'Signal Beta';
|
|
|
|
|
|
|
|
// -------
|
|
|
|
function checkValue(object, objectPath, expected) {
|
|
const actual = _.get(object, objectPath)
|
|
if (actual !== expected) {
|
|
throw new Error(objectPath + ' was ' + actual + '; expected ' + expected);
|
|
}
|
|
}
|
|
|
|
// ------
|
|
|
|
checkValue(packageJson, NAME_PATH, PRODUCTION_NAME);
|
|
checkValue(packageJson, PRODUCT_NAME_PATH, PRODUCTION_PRODUCT_NAME);
|
|
checkValue(packageJson, APP_ID_PATH, PRODUCTION_APP_ID);
|
|
checkValue(packageJson, STARTUP_WM_CLASS_PATH, PRODUCTION_STARTUP_WM_CLASS);
|
|
|
|
// -------
|
|
|
|
_.set(packageJson, NAME_PATH, BETA_NAME);
|
|
_.set(packageJson, PRODUCT_NAME_PATH, BETA_PRODUCT_NAME);
|
|
_.set(packageJson, APP_ID_PATH, BETA_APP_ID);
|
|
_.set(packageJson, STARTUP_WM_CLASS_PATH, BETA_STARTUP_WM_CLASS);
|
|
|
|
// -------
|
|
|
|
fs.writeFileSync('./package.json', JSON.stringify(packageJson, null, ' '));
|