2 commits

Author	SHA1	Message	Date
Richard Zhao	011ae3fd52	Add support for environment variables in config (#534) ... * Allow env to be specified in config (#424) This is referencing #424. User specified environment variables in the `.hyperterm.js` file are expected under a field named `env`. An example config: ``` module.exports = { config: { ... // Environment variables env: { WHAT_UP: 'heyo', } ... }, plugins: [], localPlugins: [] }; ``` * Add env field to default config	2016-08-02 08:49:25 +01:00
Guillermo Rauch	aaed99abac	Reorg (#386) ... * Step 1: move electorn into `app/`. This is to comply with the suggested directory format of `electron-builder`: https://github.com/electron-userland/electron-builder#two-packagejson-structure * Step 2: add build directory with icon files for mac / windows * Step 3: move all development (web) assets into main directory * Step 4: add `build` namespace to dev `package.json` * Step 5: move all dev dependencies into dev file and get rid of old electron packagers in favor of `eletorn-builder` * Step 6: target build inside `app/` as everything else is excluded at build time * Step 7: remove old stuff! * Step 8: update README * turn off asar for `child_pty`	2016-07-24 10:59:21 -07:00

Renamed from config-default.js (Browse further)