Please it's delivery of new QPKG : Syncthing 0.14.4
IF you have already installed Syncthing ... please use the internal update mechanism proposed ...
IT'S A MAJOR UPDATE
ALL nodes MUST BE updated at same time (no coexistence )
ANDROID client MUST see here : http://forum.qnap.com/viewtopic.php?f=3 ... 35#p515858
Please read carefully ... some specific to QNAP integration
Syncthing replaces proprietary sync and cloud services with something open, trustworthy and decentralized. Your data is your data alone and you deserve to choose where it is stored, if it is shared with some third party and how it's transmitted over the Internet
... update syncthing (for new user or restore afrter a crash auto-update will work for others)
... inotify update to 0.8.3
... relaysrv NOW strelaysrv update
... discovery server is no more needed (integrated in Synncthing)
... update syncthing (for new user or if internal update d'ont work as well (64 bits system on kernel 3.4) )
... update relaysrv to Build 185
... update inotify to Version 0.7
Syncthing update (for new user or if internal update d'ont work as well)
... also update of inotify to 0.6.8
==== Add discosrv
==== update syncthing, syncthing-inotify, relaysrv
==== ADD support for TAS-x68 series =======
MAJOR UPDATE to 0.12 new version ...
ALL NODES MUST be changed at the same period ...
syncthing-inotify for 0.12
NEW strelaysrv (it's a private relay server to manage access from syncthing when you are behind a firewall without possibility to open port ...) public relay server exist with Public or private you can synchronize data even from a node inside office with only port 443 open in output ...
====== CHANGE =====
QPKG 126.96.36.199 (last for version 11 family)
Update of syncthing
====== CHANGE =======
... cli and notify for armel are NOW usable (the problem was that now it's no more possible (or easy) to build exec for other plate-form only native ...
... IDEM syncthing.amd64.static ... IS NO MORE AVAILABLE
... ... so to have auto-update use the 386 version or wait for my own update
For system with a x86_64 kernel ... I will now provide the 2 binary (x86_64 ... with lib ; and x86 without lib (static))
... add an option to set the x86 or the 64 bits version (it's for users where auto-update don't work with the 64 bits version)
... this work ONLY on x86_64 system with 64 bits kernels
syncsh set_x86 or set_x86_64 ... this change executable and restart syncthing ... so you can switch between
status is reported in
update syncthing to 0.10.20
*** Same version NOW for all Arm models
*** In QPKG directory a PDF file (Getting Started)
[QNAP's model supported]
ALL except old Arm x09 family
Install choice version based on kernel ...
x86-64 (NATIVE 64 bits) for 809, x69, x70, x51/53, x59 (starting with 459), etc.
x86 (32 bits) for 509, x39, 259 ...
Armv5 for Arm series x10, x12, x19, x20 etc. except x31 ...
Armv7 for Arm series x31 and TAS-x68
[Other platform supported by syncthing (not supply in QPKG)]
Others Linux x86 / x86_64
others armv5 , armv6, armv7
[External Links ]
License, documentation, source code, credits : http://syncthing.net/
GETTING STARTED : https://discourse.syncthing.net/t/getting-started/46 (bypass installation)
ALSO provide as a PDF in QPKG folder (obtain using command : getcfg syncthing Install_Path -f /etc/config/qpkg.conf )
GUI use the language of your browser ... so languages are supported (English, French, etc.) tested ONLY with Chrome
Web GUI Port used : 8090 accessible from ALL I.P. ATTENTION this is change using syncthing.conf file in QPKG folder NOT inside the product ... so value in GUI are still the default one 127.0.0.1 (localhost) 8080 ( changed ... because ... generally used by QNAP web admin)
User : only admin for the moment (in future release you can choice the user)
Upnpc : upnpc IGD network forwarding / mapping work as well (with compatible router) BUT use GUI to use it or not, verify if it's work on your own network ... YOU DON'T need it if you use only your internal network
config.xml file is in : /share/XXX_DATA/.qpkg/syncthing (XXX can be HDA, MD0, CACHEDEV1 etc.) or get the folder path using : getcfg syncthing Install_Path -f /etc/config/qpkg.conf
UPDATE QPKG 1.0
Change HOME folder to QPKG syncthing folder (NO MORE using /root )
Suppress any thing to do with default folder NOW in QPKG_FOLDER/Sync
ADD daemon-mgr task management (so on restart a delai from 0 to 30 sec can be done ...
ADD Rotate Log ... default YES ... in QPKG folder (when all run set Log OFF to avoid disk spin-down
ADD HTTPS access through Web Admin SSL Port (so can share certificate (unsigned or signed) with QNAP system
Support of AUTO update (internal) and specific command to update the syncthing version in qpkg.conf file
Command available :
Code: Select all
Usage is :
/usr/bin/syncsh status [full]
/usr/bin/syncsh set_log|unset_log (need a restart to be use
AFTER internal Update you can change Syncthing version in QPKG
/usr/bin/syncsh set_new_version VERSION ( example VERSION = 0.9.10 check in GUI after internal update )
UPDATE Syncthing to 0.9.10 ...
READ THE DOCUMENTATION ... read the documentation, read the documentation ...
INSTALL : please wait some delay before using the Syncthing Web Interface (Arm is more concerned) ... because at FIRST RUN ... Syncthing create certificate ... so take up to 30sec on Arm, BUT it's during the first run only
If you want a private syncthing network ... deactivate "Global Announcement" (Gui)
If you are in an internal network only ... suppress upnp (Gui)
If you add a user / password to close Web Gui access and lost it ... clear 2 corresponding lines in config.xml file in the "gui" section.
ATTENTION ... folder is scanned and data and index are encrypted using AES ... transfert use TLS ... SO this can consume LOT of CPU and memory in case of large folders and files ... with Arm system please get attention to this CPU / memory point ...
YOU CAN change the scanning delay (to search new or modified files) ... for the moment it is MANUALLY in config.xml BUT it's a REAL GOOD IDEA for Arm and low processor models
ATTENTION the first scan and encryption can take a long time for large (quantity and/or size) files
ALSO TAKE attention to your network capacity (ex. some ADSL have a small output throughput ... )
IMPORTANT optionaly you can define Folder as MASTER ... so change affect clone NOT the original
ATTENTION ... rescan of Upnp IGD is 30 mns ... change it in config.xml file if you want to increase it
ATTENTION ... seems that ONLY real folder can be used for synchronisation ... so don't use Link (T.B.C.)
Internal HTTPS can be used BUT ... this generate others UNSIGNED certificate ... so you can have to accept the exception ... the URL is same as previous BUT HTTPS
... this internal change is not reflected in QTS desktop (next release) better is to use the Apache SSL system Proxy ... so same certificate as QNAP's are used ... so also signed certificate if you own one and integrate in QNAP system.
TS-x53, TS-x69, TS-x59, TS-x19 (Armv5), TS-x31 (Armv7) , TAS-168 (armv7)
1-0.14.4 : https://www.father-mande.ovh/Q/qpkg/syn ... 0.14.4.zip
1-0.12.22 : https://mega.nz/#!NptUSCCQ!21iYx7FkJUeJ ... 6xHCshsfDY
1-0.12.19 : https://mega.nz/#!JgMVgByK!LeJITyv2P4HO ... d3iScyhPgs
download others versions ... Windows, Mac, Linux, Bsd, etc.
https://github.com/syncthing/syncthing/ ... ag/v0.14.4
Android : http://forum.qnap.com/viewtopic.php?f=3 ... 35#p515858
PLEASE return experience ... for the product ... I don't support it ... it's supported by Syncthing team