![]() ![]() Will receive this notification and immediately perform a ‘down’ command. Clients subscribed to the repository’s channel Is published to the pub/sub server, telling other clients of this repo Registered, the command waits a few seconds (waiting for settlement) and Locally synced folder (and all of its subfolders). Syncany pub/sub server and registers local file system watches in the In the default configuration (no options), the command subscribes to the TheĬommand performs the up and down command in an interval, watches theįile system for changes and subscribes to the Syncany pub/sub server. sy watch: Automatically synchronizes the local folder with the repo ¶Īutomatically synchronizes the local folder with the repository. The daemon configuration can be found at %AppData%\Syncany\daemon.xml (Windows) or at ~/.config/syncany/daemon.xml (Linux).ĥ.9. That means that it does not run as system service, but rather that each user may have its own daemon process running and that the daemon config is user-specific. The Syncany daemon is a user-level daemon. force-stop: Kills the Syncany daemon can be used if stop doesn’t respond (Linux only).reload: Reloads the daemon configuration ( daemon.xml) without restarting the daemon (Linux only).restart: Restarts the daemon process by calling stop, then start (Linux only).status: Displays whether the daemon is running and if it is, its PID.stop: Stop the Syncany daemon (if it is running).start: Starts the Syncany background process (daemon), if it’s not already running.The command itself only offers the typical start/stop-script sub-commands, namely: This command manages the Syncany background process (starts, stops, etc.), also called the Syncany daemon. sy daemon: Start and stop the background process (daemon) ¶ The only command that doesn’t care where it’s executed is the plugin command.įor a detailed command reference including all command-specific options, please refer to the manual page of this command at sy / syncany.ĥ.2. Most of the other commands behave exactly opposite to that: The commands status, up, ls-remote, down, watch, cleanup, restore, genlink and ls can only be execute inside an initialized Syncany folder. daemon: Start and stop the background process (daemon)īecause the init and connect command initialize the current folder to a Syncany folder, they cannot be executed inside an already initialized Syncany folder.plugin: List, install and remove storage backend plugins.ls: Lists and filters the current and past file tree.genlink: Create a syncany:// link from an existing local folder.restore: Restore the given file paths from the remote repository.cleanup: Remove old versions from the local database and the repo.watch: Automatically synchronizes the local folder with the repo.down: Detect remote changes and apply locally.ls-remote: List changes on remote repository.up: Detect local changes and upload to repository.status: List new and changed files in local Syncany folder.connect: Connect the current folder to an existing Syncany repository.init: Initialize the current folder as a Syncany folder.In general, it can be called by sy, where action is any of the available sub-commands and args is a list of optional global or sub-command specific options. The sy command is not just a single command, but instead offers a variety of actions to manage a Syncany folder. sy plugin: List, install and remove storage backend plugins sy genlink: Create a syncany:// link from an existing local folder sy ls: Display current and historic local database sy restore: Restore older versions of files from the repository sy cleanup: Remove old versions from the local database and the repo sy watch: Automatically synchronizes the local folder with the repo sy down: Retrieve and apply remote changes sy ls-remote: Detect and display remote changes sy up: Detect local changes and upload to repository sy status: Detect and display local changes sy connect: Connecting to an existing repository sy daemon: Start and stop the background process (daemon) Differences and similarities to other tools Trace-based synchronization through vector clocks Privacy by design through client-side encryption Minimizing remote disk space through deduplication Abstraction for dumb storage through a minimal API
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |