History

Jakob Borg 22e44642a0 next-gen-gui: Add button to restore default theme (#7433 ) This adds a button in the top right that changes the config back to the default theme. Code wise, it takes the header that was previously a part of the dashboard component and moves it to the app component, and then adds the button there. Possibly the header should be a component of it's own, but that's more of refactor that can happen separately I think. The config change uses the new config API to just patch the relevant setting. I'm not doing an automatic reload because 1) I don't want to figure out how to do it correctly and 2) this doesn't work reliably anyway, as for example the current gen GUI does a reload and ends up with connection refused as the API service is still reloading...		2021-03-08 12:54:08 +01:00
..
e2e	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
src	next-gen-gui: Add button to restore default theme (#7433 )	2021-03-08 12:54:08 +01:00
.editorconfig	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
.gitignore	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
LICENSE	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
README.md	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
angular.json	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
browserslist	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
karma.conf.js	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
package-lock.json	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
package.json	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
screenshot.png	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
tsconfig.app.json	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
tsconfig.json	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
tsconfig.spec.json	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
tslint.json	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00

README.md

Syncthing Tech UI

Usage

This is a very bare bones read-only GUI for viewing the status of large setups. Download a release zip and unpack it into the GUI override directory (assuming default Linux setup):

$ cd ~/.config/syncthing
$ mkdir -p gui/default
$ cd gui/default
$ unzip ~/tech-ui-v1.0.0.zip

Then load the GUI via http://localhost:8384/tech-ui/ or similar. You should see something like this:

Development server

Run npm run serve for a dev server. Navigate to http://localhost:4200/. The app will automatically reload if you change any of the source files.

Production server

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 Syncthing's config directory.

$ 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 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

License

MPLv2