octoleo/syncthing
1
0
Fork 0
mirror of https://github.com/octoleo/syncthing.git synced 2024-11-14 01:04:14 +00:00
Code Issues Packages Projects Releases Wiki Activity

Also mention STGUIASSETS

Browse Source
This commit is contained in:
Jakob Borg 2020-03-31 16:14:09 +02:00
parent 192e843989
commit 33398b0b6b
1 changed files with 17 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

19
README.md
View File

@ -11,12 +11,27 @@ In production we serve the UI through Syncthing itself. The easiest way to
do that is to simply put the built assets in the `gui` subdirectory of do that is to simply put the built assets in the `gui` subdirectory of
Syncthing's config directory. Syncthing's config directory.
- `npm run build -- --prod` ```
- `rsync -va --delete dist/tech-ui/ ~/.config/syncthing/gui/default/tech-ui/` $ npm run build -- --prod
$ rsync -va --delete dist/tech-ui/ ~/.config/syncthing/gui/default/tech-ui/
```
Adjust for your actual Syncthing config dir if different. Navigate to Adjust for your actual Syncthing config dir if different. Navigate to
`http://localhost:8384/tech-ui/`. `http://localhost:8384/tech-ui/`.
Another option is to start Syncthing with the STGUIASSETS environment
variable pointing to the distribution directory.
```
$ npm run build -- --prod
$ ln -sf . dist/default
$ export STGUIASSETS=$(pwd)/dist
$ syncthing
```
The magic is symlink is because Syncthing will look for the GUI in the
`default` subdirectory. Navigate to `http://localhost:8384/tech-ui/`.
## Code scaffolding ## Code scaffolding
Run `ng generate component component-name` to generate a new component. You Run `ng generate component component-name` to generate a new component. You