History

Jakob Borg 439c6c5b7c lib/api: Add cache busting for basic auth (ref #9208 ) (#9215 ) This adds our short device ID to the basic auth realm. This has at least two consequences: - It is different from what's presented by another device on the same address (e.g., if I use SSH forwards to different dives on the same local address), preventing credentials for one from being sent to another. - It is different from what we did previously, meaning we avoid cached credentials from old versions interfering with the new login flow. I don't think there should be things that depend on our precise realm string, so this shouldn't break any existing setups... Sneakily this also changes the session cookie and CSRF name, because I think `id.Short().String()` is nicer than `id.String()[:5]` and the short ID is two characters longer. That's also not a problem...		2023-11-14 11:57:39 +01:00
..
e2e	build: Add build process for newgui (#7351 )	2021-02-15 14:52:28 +01:00
src	lib/api: Add cache busting for basic auth (ref #9208 ) (#9215 )	2023-11-14 11:57:39 +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