-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
syncthing: update to v1.23.4 and include next-gen-gui #5523
Conversation
@acolomb I plan to add configuration of a shared folder to the installation wizard. This folder will be used as the default sync folder. Currently the package var folder is used as HOME and therefore the default sync folder (for sc-syncthing service user). As reported in #3320 this folder is not accessible by DSM users. A shared folder will be supported by DSM to configure dedicated user permissions. I already updated syncthing in this PR to not create the default folder at first service start. Any hint is appreciated, as I am not a syncthing user. |
Well, Syncthing doesn't have or need the concept of one main folder, as it can be pointed at any accessible path in the file system. The default folder is basically just to help get people jump-started on the Desktop. It doesn't really make sense on a NAS I think, where the purpose is usually to synchronize files which are also used by other applications or sharing protocols. Thus the most sensible solution would be to just disable creating the default folder, via If you want to add a "share" through the wizard, where would that be stored and how could other apps access it? I don't see how creating an empty default folder under a new share really helps with using Syncthing on the NAS. The default folder can be removed from Syncthing anytime, but the share will stay around, for what purpose? |
@acolomb I am not happy with the creation of a shared folder. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like how the HOME variable can be overridden now, but I seriously doubt anyone will use it. The template folder path can already be adjusted directly in the Web GUI, and therefore $HOME
is only relevant for the meaning of ~
.
I haven't tested any of this yet, just looked at the code.
f6c693d
to
d341c68
Compare
@hgy59 This should be updated to the latest Syncthing v1.23.0 (or whatever is the latest stable) release before merging. |
@hgy59 I've now successfully built the package for aarch64, including the next-gen-gui, with Go 1.19.5. It took about four minutes mainly because of all the NPM stuff going on. Frankly I don't even know what even needs "building" there, the usual GUI just works from the Git repo state. So I repeat my request to please leave this If anyone wants to use the "tech-ui", it's as simple as unzipping its build to the theme folder (we can keep the introduced |
3241f18
to
808dc7a
Compare
- update syncthing to v1.22.2 - include next-get-gui and provide it under /tech-ui - fix parameter of ca_reloader.sh - fix link in wizard files
- avoid the creation of a default folder on first startup
…irst start of syncthing
Co-authored-by: André Colomb <github.com@andre.colomb.de>
Co-authored-by: André Colomb <github.com@andre.colomb.de>
- avoid the use of '--home' argument as not related to HOME env. variable - enable to define custom HOME folder in options.conf
- add customization information to wizard - fix install_uifile_fre (add wizard_username and wizard_password) - add information for options.conf.new to upgrade wizard
Co-authored-by: André Colomb <github.com@andre.colomb.de>
- omit to compile synchthing --with-next-gen-gui
808dc7a
to
9c9c0dc
Compare
@acolomb this should be ready to merge now |
Let me take a look tonight or tomorrow probably. |
don't hurry, I will be offline for about a week. (BTW i removed the nodejs dependency by adding prebuilt tech-ui). |
@acolomb just a friendly reminder to have a look at this PR. |
Thanks @hgy59 and sorry for taking so long. I've had some unforeseen things to take care of lately so didn't get a chance to look at code. Hopefully this week. |
If the "next gen UI" is a sticking point, can we please just perform an upgrade to v1.23.1 and relegate the UI to another PR? |
I just didn't find the time to review again, but it's not forgotten and I will try to get it done very soon. Before we merge, v1.23.3 just came out, so better include that latest version before merging. However a bug (syncthing/syncthing#8851) was just found which may lead to another point release in the next few days, will keep you posted on that. Note that you should be on Syncthing v1.23.3 already if you haven't disabled the internal upgrade mechanism. The packaged binary keeps itself up to date regardless of the SPK package version. |
Thanks! I forgot that I had disabled the updater. All is working well now with v1.23.4 on my DS212j. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good except for needing an upgrade to v1.23.4 now. Suggestions included to carry that out. Otherwise just a simple needless whitespace change.
Co-authored-by: André Colomb <github.com@andre.colomb.de>
Co-authored-by: André Colomb <github.com@andre.colomb.de>
Co-authored-by: André Colomb <github.com@andre.colomb.de>
Co-authored-by: André Colomb <github.com@andre.colomb.de>
- avoid running ca_reloader.sh on DSM 7+
Description
Fixes #5289
Checklist
all-supported
completed successfullyType of change