You have the option of starting your ownCloud desktop client with the owncloud command. The following options are supported:
The other options are:
)
The ownCloud Client reads a configuration file. You can locate this configuration file as follows:
The configuration file contains settings using the Microsoft Windows .ini file format. You can overwrite changes using the ownCloud configuration dialog.
Note
Use caution when making changes to the ownCloud Client configuration file. Incorrect settings can produce unintended results.
Some interesting values that can be set on the configuration file are:
[ownCloud] section | ||
---|---|---|
Variable | Default | Meaning |
remotePollInterval | 30000 | Specifies the poll time for the remote repository in milliseconds. |
forceSyncInterval | 7200000 | The duration of no activity after which a synchronization run shall be triggered automatically. |
fullLocalDiscoveryInterval | 3600000 | The interval after which the next synchronization will perform a full local discovery. |
notificationRefreshInterval | 300000 | Specifies the default interval of checking for new server notifications in milliseconds. |
[General] section | ||
---|---|---|
Variable | Default | Meaning |
chunkSize | 5242880 | Specifies the chunk size of uploaded files in bytes. |
promptDeleteAllFiles | true | If a UI prompt should ask for confirmation if it was detected that all files and folders were deleted. |
maxLogLines | 20000 | Specifies the maximum number of log lines displayed in the log window. |
timeout | 300 | The timeout for network connections in seconds. |
moveToTrash | false | If non-locally deleted files should be moved to trash instead of deleting them completely. This option only works on linux |
showExperimentalOptions | false | Whether to show experimental options that are still undergoing testing in the user interface. Turning this on does not enable experimental behavior on its own. It does enable user inferface options that can be used to opt in to experimental features. |
[Proxy] section | ||
---|---|---|
Variable | Default | Meaning |
host | 127.0.0.1 | The address of the proxy server. |
port | 8080 | The port were the proxy is listening. |
type | 2 | 0 for System Proxy. |
1 for SOCKS5 Proxy. | ||
2 for No Proxy. | ||
3 for HTTP(S) Proxy. |
The behavior of the client can also be controlled using environment variables. The value of the environment variables overrides the values in the configuration file.
The environment variables are:
The ownCloud Client packages contain a command line client, owncloudcmd, that can be used to synchronize ownCloud files to client machines.
owncloudcmd performs a single sync run and then exits the synchronization process. In this manner, owncloudcmd processes the differences between client and server directories and propagates the files to bring both repositories to the same state. Contrary to the GUI-based client, owncloudcmd does not repeat synchronizations on its own. It also does not monitor for file system changes.
To invoke owncloudcmd, you must provide the local and the remote repository URL using the following command:
owncloudcmd [OPTIONS...] sourcedir owncloudurl
where sourcedir is the local directory and owncloudurl is the server URL.
Other command line switches supported by owncloudcmd include the following:
owncloudcmd requires the user to specify the username and password using the standard URL pattern, e.g.,
$ owncloudcmd /home/user/my_sync_folder https://carla:secret@server/owncloud/remote.php/webdav/
To synchronize the ownCloud directory Music to the local directory media/music, through a proxy listening on port 8080, and on a gateway machine using IP address 192.168.178.1, the command line would be:
$ owncloudcmd --httpproxy http://192.168.178.1:8080 \
$HOME/media/music \
https://server/owncloud/remote.php/webdav/Music
owncloudcmd will prompt for the user name and password, unless they have been specified on the command line or -n has been passed.
owncloudcmd requires access to an exclude list file. It must either be installed along with owncloudcmd and thus be available in a system location, be placed next to the binary as sync-exclude.lst or be explicitly specified with the --exclude switch.
When disk space is low the ownCloud Client will be unable to synchronize all files. This section describes its behavior in a low disk space situation as well as the options that influence it.