You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
npm install --global yarn # (only if you don’t already have `yarn`)
62
62
yarn install --frozen-lockfile # Install and build dependencies (this will take a while)
63
-
yarn grunt # Generate final JS and CSS assets
64
-
yarn icon-gen # Generate full set of icons for Electron
63
+
yarn build-everything
65
64
yarn test # A good idea to make sure tests run first
66
-
yarn start # Start Session!
65
+
yarn start-prod # Start Session!
67
66
```
68
67
69
68
You'll need to restart the application regularly to see your changes, as there
@@ -72,14 +71,10 @@ is no automatic restart mechanism. Alternatively, keep the developer tools open
72
71
<kbd>Cmd</kbd> + <kbd>R</kbd> (macOS) or <kbd>Ctrl</kbd> + <kbd>R</kbd>
73
72
(Windows & Linux).
74
73
75
-
Also, note that the assets loaded by the application are not necessarily the same files
76
-
you’re touching. You may not see your changes until you run `yarn grunt` on the
77
-
command-line like you did during setup. You can make it easier on yourself by generating
78
-
the latest built assets when you change a file. Run this in its own terminal instance
79
-
while you make changes:
80
-
81
74
```
82
-
yarn grunt dev # runs until you stop it, re-generating built assets on file changes
75
+
yarn build-everything:watch # runs until you stop it, re-generating built assets on file changes
76
+
# Once this command is waiting for changes, you will need to run in another terminal `yarn parcel-util-worker` to fix the "exports undefined" error on start.
77
+
# If you do change the sass while this command is running, it won't pick it up. You need to either run `yarn sass` or have `yarn sass:watch` running in a separate terminal.
83
78
```
84
79
85
80
## Multiple instances
@@ -93,8 +88,6 @@ directory from `%appData%/Session` to `%appData%/Session-{environment}-{instance
93
88
There are a few scripts which you can use:
94
89
95
90
```
96
-
yarn start - Start development
97
-
MULTI=1 yarn start - Start second instance of development
98
91
yarn start-prod - Start production but in development mode
99
92
MULTI=1 yarn start-prod - Start another instance of production
100
93
```
@@ -103,7 +96,7 @@ For more than 2 clients, you may run the above command with `NODE_APP_INSTANCE`
103
96
For example, running:
104
97
105
98
```
106
-
NODE_APP_INSTANCE=alice yarn start
99
+
NODE_APP_INSTANCE=alice yarn start-prod
107
100
```
108
101
109
102
Will run the development environment with the `alice` instance and thus create a seperate storage profile.
@@ -188,6 +181,6 @@ see how they did things.
188
181
You can build a production binary by running the following:
"sendRecoveryPhraseMessage": "You are attempting to send your recovery phrase which can be used to access your account. Are you sure you want to send this message?",
"sendRecoveryPhraseMessage": "You are attempting to send your recovery phrase which can be used to access your account. Are you sure you want to send this message?",
"sendRecoveryPhraseTitle": "Odesílání fráze pro obnovení",
391
389
"sendRecoveryPhraseMessage": "Pokoušíš se odeslat svou frázu pro obnovení, díky které se lze přihlásit do tvého účtu. Opravdu chceš tuto zprávu odeslat?",
0 commit comments