2017-06-21 18:04:19 -07:00
|
|
|
const path = require('path');
|
|
|
|
|
Beta versions support: SxS support, in-app env/instance display (#1606)
* 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
2017-10-30 13:57:13 -07:00
|
|
|
const packageJson = require('../package.json');
|
2017-06-21 18:04:19 -07:00
|
|
|
|
Beta versions support: SxS support, in-app env/instance display (#1606)
* 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
2017-10-30 13:57:13 -07:00
|
|
|
|
|
|
|
const environment = packageJson.environment || process.env.NODE_ENV || 'development';
|
2017-06-21 18:04:19 -07:00
|
|
|
|
|
|
|
// Set environment vars to configure node-config before requiring it
|
|
|
|
process.env.NODE_ENV = environment;
|
|
|
|
process.env.NODE_CONFIG_DIR = path.join(__dirname, '..', 'config');
|
|
|
|
|
|
|
|
if (environment === 'production') {
|
|
|
|
// harden production config against the local env
|
|
|
|
process.env.NODE_CONFIG = '';
|
|
|
|
process.env.NODE_CONFIG_STRICT_MODE = true;
|
|
|
|
process.env.HOSTNAME = '';
|
|
|
|
process.env.NODE_APP_INSTANCE = '';
|
|
|
|
process.env.ALLOW_CONFIG_MUTATIONS = '';
|
|
|
|
process.env.SUPPRESS_NO_CONFIG_WARNING = '';
|
|
|
|
}
|
|
|
|
|
|
|
|
const config = require('config');
|
|
|
|
config.environment = environment;
|
|
|
|
|
|
|
|
// Log resulting env vars in use by config
|
|
|
|
[
|
|
|
|
'NODE_ENV',
|
|
|
|
'NODE_CONFIG_DIR',
|
|
|
|
'NODE_CONFIG',
|
|
|
|
'ALLOW_CONFIG_MUTATIONS',
|
|
|
|
'HOSTNAME',
|
|
|
|
'NODE_APP_INSTANCE',
|
|
|
|
'SUPPRESS_NO_CONFIG_WARNING'
|
|
|
|
].forEach(function(s) {
|
|
|
|
console.log(s + ' ' + config.util.getEnv(s));
|
|
|
|
});
|
|
|
|
|
|
|
|
module.exports = config;
|