experiments in a post-browser web
use separate profiles for packaged vs source runs
- Packaged app uses 'default' profile (production)
- Running from source uses 'dev' profile (development)
- PROFILE env var still allows manual override
+7
-6
+7
-6
index.js
+7
-6
index.js
···
69
69
}
70
70
};
71
71
72
-
const p = process.env.PROFILE;
73
-
console.log('env prof?', p, p != undefined, typeof p)
74
72
const profileIsLegit = p => p != undefined && typeof p == 'string' && p.length > 0;
75
73
76
-
const PROFILE =
77
-
profileIsLegit(process.env.PROFILE)
74
+
// Profile selection:
75
+
// 1. Explicit PROFILE env var takes precedence
76
+
// 2. Packaged app uses 'default' (production)
77
+
// 3. Running from source uses 'dev' (development)
78
+
const PROFILE = profileIsLegit(process.env.PROFILE)
78
79
? process.env.PROFILE
79
-
: (DEBUG == true ? 'debug' : 'default');
80
+
: (app.isPackaged ? 'default' : 'dev');
80
81
81
-
console.log('PROFILE', PROFILE);
82
+
console.log('PROFILE', PROFILE, app.isPackaged ? '(packaged)' : '(source)');
82
83
83
84
// Profile dirs are subdir of userData dir
84
85
// ..................................... ↓ we set this per profile