Owncloud linux console client

ownCloud command line client owncloudcmd

The ownCloud documentation mentions a command line client owncloudcmd which is supposed to be installed as part of the ownCloud Client package.

I have the owncloud-client package from the official repositories installed on Ubuntu 18.04 (version 2.4.1). The GUI client works but I cannot find this owncloudcmd executable.

Does anybody know why the Ubuntu package doesn’t contain owncloudcmd , and how I can install it?

1 Answer 1

They split the package in two:

The latter doesn’t depend on the GUI program, which probably is why they split the two – on a headless system you don’t need the GUI, so no need to install it. To use owncloudcmd you just need to install the aforementioned package:

On Ubuntu 18.04 this installs version 2.4.1 of the program. If for any reason you need the current version 2.4.2 and/or updates to the current version at any time, I recommend installing the Ubuntu PPA from software.opensuse.org. Follow these steps to set it up and install the package (I simplified this a bit):

Remove the repository package (you may skip this step if you didn’t install it):

Add the repository:

Add the repository key:

Update the sources and install the newest package version available. As the PPA‘s version is newer, this ignores the official repository’s owncloud-client package:

After this owncloud and most notably owncloudcmd work out of the box:

Источник

Как настроить синхронизацию с linux console на сервер OwnCloud?

Доброго времени всем.
Не могу настроить синхронизацию с сервером OwnCloud через клиет
При вводе команды «owncloudcmd» выдает сообщение «Usage: owncloudcmd
»
пишу как по ману
Usage: owncloudcmd /home/user/folder1 h t t p s://cloud.domen.com/owncloud/

Я так понимаю мне нужно создать конфигурационный файл синхронизации, подскажите где его создавать и какой пример его транскрипции. Спасибо

• Вопрос задан более трёх лет назад
• 754 просмотра

Андрей Буров: обновил
apt-cache search owncloud

/extreme# apt-cache search owncloud
csync-owncloud — user level bidirectional client only file synchronizer
gnome-online-miners — Crawls through your online content
libcsync-dev — library for user level bidirectional client only file synchronizer
libcsync-plugin-owncloud — OwnCloud plugin for csync
libcsync-plugin-sftp — SFTP plugin for csync
libcsync-plugin-smb — SMB plugin for csync
libcsync0 — library for user level bidirectional client only file synchronizer
libocsync-dev — development files for ocsync
libocsync0 — library for user level bidirectional client only file synchronizer
libowncloudsync0 — ownCloudSync folder synchronization — libraries
mirall-doc — transitional dummy package for owncloud-client-doc
mirall-l10n — transitional dummy package for owncloud-client-l10n
owncloud-client — folder synchronization with an ownCloud server — GUI
owncloud-client-cmd — folder synchronization with an ownCloud server — cmd client
owncloud-client-doc — ownCloudSync folder synchronization — documentation
owncloud-client-l10n — ownCloudSync folder synchronization — localization
owncloud-doc — documentation for ownCloud
python-owncloud — ownCloud CLI client
owncloud — empty package

Источник

The Command Line Client

Introduction

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:

sourcedir is the local directory and owncloudurl is the server URL. Other command line switches supported by owncloudcmd include the following:

Use user as the login name.

—password , -p [password]

Use password as the password.

Use netrc (5) for login.

Do not prompt for questions.

Inhibits verbose log output.

Trust any SSL certificate, including invalid ones.

Uses server as HTTP proxy.

Overrides the WebDAV Path with path

Exclude list file.

File containing the list of un-synced remote folders (selective sync)

Retries maximum n times (defaults to 3)

Sync hidden files,do not ignore them.

Credential Handling

owncloudcmd requires the user to specify the username and password using the standard URL pattern, for example:

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 will prompt for the user name and password, unless they have been specified on the command line or -n has been passed.

Источник

Make a console only version of the owncloud client #226

Comments

eedgar commented Jan 7, 2013

I have a linux server that I would like to use owncloud with. However I do not have X installed and do not wish to install X to configure owncloud.

The text was updated successfully, but these errors were encountered:

danimo commented May 1, 2013

erenoglu commented Apr 20, 2014

since pyowncloud doesn’t anymore work with recent versions of ocsync, this bug shall be re-opened.
I’m facing the same problem. I want to build mirall command line only without any qt stuff, how can i do it?

dragotin commented Apr 22, 2014

The command line tool is called owncloudcmd and is delivered with the client, see also https://github.com/owncloud/mirall/blob/master/doc/owncloudcmd.rst

It uses «qt stuff» as you call it tough, but that wont change and should not be a problem.

blackcobra1973 commented Feb 24, 2015

For me qt stuff is a big problem. I want to have a nice clean setup and be able to sync certain folders with certain servers which do not have any X library available so qt stuff does not work so no owncloudcmd because it requires lots of X library’s so please make just like dropbox/seafile a command line only client. So please reopen this ticket or I just create a new one.

danimo commented Feb 24, 2015

@blackcobra1973 Every aspect of the client is written with «the Qt stuff». But Qt is not a gui-only toolkit. Anyway, For now there is owncloudcmd.

blackcobra1973 commented Feb 24, 2015

Yes and my customer who I am preparing the POC’s for has a requirement for a full command line version without all the x stuff that come in with QT. So I have a feeling they will cancel the POC for owncloud and the decision will happen between dropbox/bittorent sync/seafile.

And yes owncloudcmd is full of X stuff: ldd /usr/bin/owncloudcmd
linux-vdso.so.1 => (0x00007fff28fec000)
libowncloudsync.so.0 => /lib64/libowncloudsync.so.0 (0x00007fb6f7974000)
libQtWebKit.so.4 => /lib64/libQtWebKit.so.4 (0x00007fb6f5605000)
libQtXmlPatterns.so.4 => /lib64/libQtXmlPatterns.so.4 (0x00007fb6f4fbd000)
libQtGui.so.4 => /lib64/libQtGui.so.4 (0x00007fb6f42e1000)
libQtDBus.so.4 => /lib64/libQtDBus.so.4 (0x00007fb6f4062000)
libQtXml.so.4 => /lib64/libQtXml.so.4 (0x00007fb6f3e1e000)
libQtSql.so.4 => /lib64/libQtSql.so.4 (0x00007fb6f3bde000)
libQtNetwork.so.4 => /lib64/libQtNetwork.so.4 (0x00007fb6f3896000)
libQtCore.so.4 => /lib64/libQtCore.so.4 (0x00007fb6f33ab000)
libocsync.so.0 => /usr/lib64/owncloud/libocsync.so.0 (0x00007fb6f3191000)
librt.so.1 => /lib64/librt.so.1 (0x00007fb6f2f88000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007fb6f2d84000)
libsqlite3.so.0 => /lib64/libsqlite3.so.0 (0x00007fb6f2acf000)
libqtkeychain.so.0 => /lib64/libqtkeychain.so.0 (0x00007fb6f28ab000)
libneon.so.27 => /lib64/libneon.so.27 (0x00007fb6f2680000)
libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007fb6f2379000)
libm.so.6 => /lib64/libm.so.6 (0x00007fb6f2076000)
libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fb6f1e60000)
libc.so.6 => /lib64/libc.so.6 (0x00007fb6f1a9f000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fb6f1882000)
libXrender.so.1 => /lib64/libXrender.so.1 (0x00007fb6f1678000)
libjpeg.so.62 => /lib64/libjpeg.so.62 (0x00007fb6f1423000)
libpng15.so.15 => /lib64/libpng15.so.15 (0x00007fb6f11f7000)
libwebp.so.4 => /lib64/libwebp.so.4 (0x00007fb6f0fa7000)
libxslt.so.1 => /lib64/libxslt.so.1 (0x00007fb6f0d68000)
libz.so.1 => /lib64/libz.so.1 (0x00007fb6f0b51000)
libgio-2.0.so.0 => /lib64/libgio-2.0.so.0 (0x00007fb6f07f5000)
libgstapp-0.10.so.0 => /lib64/libgstapp-0.10.so.0 (0x00007fb6f05e9000)
libgstinterfaces-0.10.so.0 => /lib64/libgstinterfaces-0.10.so.0 (0x00007fb6f03d6000)
libgstpbutils-0.10.so.0 => /lib64/libgstpbutils-0.10.so.0 (0x00007fb6f01b2000)
libgstvideo-0.10.so.0 => /lib64/libgstvideo-0.10.so.0 (0x00007fb6eff95000)
libgstbase-0.10.so.0 => /lib64/libgstbase-0.10.so.0 (0x00007fb6efd40000)
libgstreamer-0.10.so.0 => /lib64/libgstreamer-0.10.so.0 (0x00007fb6efa57000)
libgobject-2.0.so.0 => /lib64/libgobject-2.0.so.0 (0x00007fb6ef808000)
libgmodule-2.0.so.0 => /lib64/libgmodule-2.0.so.0 (0x00007fb6ef603000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007fb6ef401000)
libxml2.so.2 => /lib64/libxml2.so.2 (0x00007fb6ef098000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007fb6eed6e000)
libfontconfig.so.1 => /lib64/libfontconfig.so.1 (0x00007fb6eeb32000)
libfreetype.so.6 => /lib64/libfreetype.so.6 (0x00007fb6ee88d000)
libQtOpenGL.so.4 => /lib64/libQtOpenGL.so.4 (0x00007fb6ee58c000)
libGL.so.1 => /lib64/libGL.so.1 (0x00007fb6ee325000)
libXext.so.6 => /lib64/libXext.so.6 (0x00007fb6ee113000)
libX11.so.6 => /lib64/libX11.so.6 (0x00007fb6eddd4000)
libSM.so.6 => /lib64/libSM.so.6 (0x00007fb6edbcc000)
libICE.so.6 => /lib64/libICE.so.6 (0x00007fb6ed9af000)
libXi.so.6 => /lib64/libXi.so.6 (0x00007fb6ed79f000)
libXrandr.so.2 => /lib64/libXrandr.so.2 (0x00007fb6ed595000)
libXfixes.so.3 => /lib64/libXfixes.so.3 (0x00007fb6ed38e000)
libXcursor.so.1 => /lib64/libXcursor.so.1 (0x00007fb6ed183000)
libXinerama.so.1 => /lib64/libXinerama.so.1 (0x00007fb6ecf80000)
libdbus-1.so.3 => /lib64/libdbus-1.so.3 (0x00007fb6ecd37000)
libssl.so.10 => /lib64/libssl.so.10 (0x00007fb6ecacb000)
libcrypto.so.10 => /lib64/libcrypto.so.10 (0x00007fb6ec6e6000)
/lib64/ld-linux-x86-64.so.2 (0x00007fb6f7c70000)
libgnutls.so.28 => /lib64/libgnutls.so.28 (0x00007fb6ec3d5000)
libpakchois.so.0 => /lib64/libpakchois.so.0 (0x00007fb6ec1ce000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007fb6ebf83000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007fb6ebca3000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007fb6eba6e000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007fb6eb869000)
libproxy.so.1 => /lib64/libproxy.so.1 (0x00007fb6eb648000)
libexpat.so.1 => /lib64/libexpat.so.1 (0x00007fb6eb41e000)
libffi.so.6 => /lib64/libffi.so.6 (0x00007fb6eb215000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007fb6eaff0000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007fb6eadd5000)
liborc-0.4.so.0 => /lib64/liborc-0.4.so.0 (0x00007fb6eab52000)
liblzma.so.5 => /lib64/liblzma.so.5 (0x00007fb6ea92d000)
libglapi.so.0 => /lib64/libglapi.so.0 (0x00007fb6ea706000)
libXdamage.so.1 => /lib64/libXdamage.so.1 (0x00007fb6ea503000)
libX11-xcb.so.1 => /lib64/libX11-xcb.so.1 (0x00007fb6ea300000)
libxcb-glx.so.0 => /lib64/libxcb-glx.so.0 (0x00007fb6ea0e6000)
libxcb-dri2.so.0 => /lib64/libxcb-dri2.so.0 (0x00007fb6e9ee1000)
libxcb.so.1 => /lib64/libxcb.so.1 (0x00007fb6e9cbf000)
libXxf86vm.so.1 => /lib64/libXxf86vm.so.1 (0x00007fb6e9ab9000)
libdrm.so.2 => /lib64/libdrm.so.2 (0x00007fb6e98ad000)
libuuid.so.1 => /lib64/libuuid.so.1 (0x00007fb6e96a7000)
libp11-kit.so.0 => /lib64/libp11-kit.so.0 (0x00007fb6e9485000)
libtasn1.so.6 => /lib64/libtasn1.so.6 (0x00007fb6e9270000)
libnettle.so.4 => /lib64/libnettle.so.4 (0x00007fb6e903f000)
libhogweed.so.2 => /lib64/libhogweed.so.2 (0x00007fb6e8e18000)
libgmp.so.10 => /lib64/libgmp.so.10 (0x00007fb6e8ba0000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007fb6e8992000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007fb6e878e000)
libmodman.so.1 => /lib64/libmodman.so.1 (0x00007fb6e8585000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007fb6e8324000)
libXau.so.6 => /lib64/libXau.so.6 (0x00007fb6e811f000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007fb6e7ea2000)

Which I and my customer do not need on their servers.

danimo commented Feb 24, 2015

Yes, there’s still a bit of X dependencies left in libsync, which should go to a libsyncgui. Unfortunantely we cannot make this priority for us right now. We do welcome patches though and we are happy to assist.

blackcobra1973 commented Feb 24, 2015

No problem for me. I not have the time to go into the code and sort it out. I will inform my customer that this is no priority for you and that the only valuable choices are Dropbox for Business, Bittorrent Sync and Seafile they all 3 have a full client (daemon like) version ready as command line sollution.

Источник

owncloudcmd (1) — Linux Man Pages

owncloudcmd: Command line ownCloud client tool.

Command to display owncloudcmd manual in Linux: $ man 1 owncloudcmd

SYNOPSIS

owncloudcmd [ OPTIONS . ] sourcedir owncloudurl

DESCRIPTION

owncloudcmd is the command line tool used for the ownCloud file synchronization desktop utility.

Contrary to the owncloud(1) GUI client, owncloudcmd only performs a single sync run and then exits. In so doing, owncloudcmd replaces the ocsync binary used for the same purpose in earlier releases.

A sync run synchronizes a single local directory using a WebDAV share on a remote ownCloud server.

To invoke the command line client, provide the local and the remote repository: The first parameter is the local directory. The second parameter is the server URL.

NOTE: Prior to the 1.6 release of owncloudcmd, the tool only accepted owncloud:// or ownclouds:// in place of http:// and https:// as a scheme. See Examples for details.

OPTIONS

Uses server as HTTP proxy. —nonshib Uses Non Shibboleth WebDAV Authentication —davpath [path] Overrides the WebDAV Path with path —exclude [file] Exclude list file —unsyncedfolders [file] File containing the list of unsynced folders (selective sync) —max-sync-retries [n] Retries maximum n times (defaults to 3) -h Sync hidden files,do not ignore them

EXAMPLE

To synchronize the ownCloud directory Music to the local directory media/music through a proxy listening on port 8080 on the gateway machine 192.168.178.1 , the command line would be:

owncloudcmd will enquire user name and password, unless they have been specified on the command line or -n (see netrc(5) ) has been passed.

Источник