GoodSync for Linux/UNIX v 9.9.14
GoodSync for UNIX is a command line version of GoodSync that allows running GoodSync components on 32-bit and 64-bit Linux systems running on Intel processors.
These are the components provided:
* gsync -- command line version of GoodSync client.
* gs-server -- GoodSync server that serves files via GSTP protocol.
* gscp -- GoodSync file system command line client, to download / upload / rename files.
Download and Install
Version and News
GoodSync for Linux has the same version number as GoodSync for Windows, currently 9.9.14.
GoodSync for Linux is uploaded to our servers 2-3 days after GoodSync for Windows is released.
You can buy licenses for GoodSync for Linux.
Free 30-day trial is available to all new users.
gsync: How to Use
Command Line version commands and options are the same on Windows and Linux/UNIX.
Jobs are kept in file ~/.goodsync/jobs.tix which is a text file that you can modify in text editor.
More on its format in the TIX Manual.
You can copy jobs.tix file from a Windows computer and edit it or just create it on a UNIX box.
How to generate garbled password for PasswordEncrypted field: produce similar job on GS for Windows or Mac, then export it to jobs.tix, then copy PasswordEncrypted field from it.
Typical jobs.tix file for a job that syncs a folder on remote computer to a local folder via GSTP is:<Job> Name = "Remote To Local Job" Side1 = <SideOptions> Dir = <Connect> Url = "gstps://computer.user.goodsync" UserID = "user-id" PasswordEncrypted = "secret-password-garbled" </Connect> </SideOptions> Side2 = <SideOptions> Dir = <Connect> Url = "file:///home/user/folder" </Connect> </SideOptions> Direction = 1 WaitForLocks = Yes LinksOption = 1 </Job>
To see changes produced by Analyze of this job, without applying them, type:
gsync /list-changes=yes analyze "Remote To Local Job"
To Sync the job, type:
gsync sync "Remote To Local Job"
gs-server: How to Use
Documentation for GoodSync Server is provided in the GoodSync Server Manual.
Before you start using GoodSync Server, you must create Admin user account.
Admin User is the only user who can change server settings and users by directing your browser Web UI server provided by GS Server. Admin User credentials (UserID and Password) will be requested by browser when you browse to http://localhost:11000.
To create Admin user account, type:
where gs-userid is the desired Admin userid, gs-password is the desired Admin password.
gs-userid and gs-password are also credentials for GoodSync Connect, that will be used by this server, so gs-userid must be unique per GS Connect user database.
The /set-admin operation also creates ~/.goodsync/server folder and other user profile folders needed by GS server.
You can also use extended form of account creation:
System-userid is Linux userid of the use who will own files written by GS server.
You can create or modify regular non-Admin users with this command:
Another important issue to decide is whether to use GoodSync Connect infrastructure or regular static IP names/addresses to get to this server.
If you set Discovery to No then this server has static IP name/address and you will address it in GS client as gstp://myserver.mycompany.com.
If you set Discovery to Yes then this server has IP address that changes and GoodSync clients will use GoodSync Connect infrastructure to get to this server. This server shall be addressed as gstp://myserver.gs-userid.goodsync.
Server settings are stored in file ~/.goodsync/server/settings.tix which is an editable text file in TIX format.
The best way to edit it is via Web UI which is available at http://localhost:4444 via any HTML browser.
Another important configuration file is List Of Users that are authorized to connect to this server, it is stored in file ~/.goodsync/server/users.tix, also a text file in TIX format.
It must contain at least one Admin user which is referred to in settings.tix.
The Admin user (also called primary user) is allowed to change server settings via Web UI and it can access all files and folders on the server.
Credentials of Admin user are required to login to Web UI of the server.
The non-admin (secondary) users are usually limited to a specific folder on the server and it cannot change any of the server settings.
Typical settings.tix file for serving of files from the server that has static IP name (file server On, web UI on, global discovery off, local discovery off, no DAV server) is:</ServerSettings> LogLevel = 4 ConsoleLevel = 0 RetainLogDays = 10 LogFolder = "C:/ProgramData/GoodSync/server" LogPrefix = "gserver" MaxConnections = 512 RequestAuthentication = Yes OfferBasicAuth = Yes OfferDigestAuth = Yes ComputerId = "compid" Plain-Allow = Yes SSL-Allow = Yes SSL-CertificatePath = "/path-to-cert-file.crt" SSL-PrivateKeyPath = "/path-to-key-file.key" SSL-AllowedCiphers = "" GstpFileServer = Yes GstpFilePort = 33333 GstpFileLocalOnly = No GstpMapExtPortViaUpnp = No GstpExtPort = 0 LocalDiscovery = Yes GlobalDiscovery = Yes GstpManagePort = 33334 WebUiServer = Yes WebUiPort = 11000 WebUiLocalOnly = Yes DavServer = No DavPort = 22222 DavLocalOnly = Yes ForwarderServer = Yes Receiver = Yes Version = 1 </ServerSettings>
Typical users.tix file with Admin user only is:<AccountList> nAccounts = 1 <Account> UserID = "server-user-id" PasswordProt = "server-user-password-garbled" HomeFolder = "" SysUserID = "system-user-id" SysUserPwd = "" ReadOnly = No Impersonate = Yes ProtectSystem = Yes RegisterWithMediator = Yes </Account> </AccountList>
Frequently Asked Questions
Q: Is GUI version planned?
A: Not now. Command line version is produced for scripting, automation and data center operations, none of which requires a GUI.