Dies ist eine alte Version des Dokuments!
OC Basisdokumentation & Entwicklung
Fundamentals https://doc.owncloud.org/server/10.0/developer_manual/app/fundamentals/
Advanced Concepts https://doc.owncloud.org/server/10.0/developer_manual/app/advanced/
Testing Tarballs: https://download.owncloud.org/community/testing/
config.php Parameter: https://doc.owncloud.org/server/10.0/admin_manual/configuration/server/config_sample_php_parameters.html
occ Kommandos: https://doc.owncloud.com/server/admin_manual/configuration/server/occ_command.html
Installation von Kommandzeile
sudo -u www-data php occ maintenance:install --database "mysql" --database-name "owncloud2" --database-user "ocadmin" --database-pass "xxxxxxxxxxxxxxx" --admin-user "admin" --admin-pass "xxxxxxxxxxxx" --data-dir /mnt/data/ocdata2
Update & Maintenance
Maintenance Mode aktivieren (global)
sudo -u www-data php occ maintenance:mode --on
single user mode, Login nur für User der Admingruppe:
sudo -u www-data php occ maintenance:singleuser --on
Upgrade starten
sudo -u www-data php occ upgrade
Danach Maintenance Mode wieder aus
sudo -u www-data php occ maintenance:mode –-off
oder
sudo -u www-data php occ maintenance:singleuser -–off
Code integrity check
sudo -u www-data php occ integrity:check-core sudo -u www-data php occ integrity:check-app $appid
Code integrity check global abschalten:
Disable globally with 'integrity.check.disabled' ⇒ true, in config.php
Logging
Loglevel to start logging at. Valid values are: 0 = Debug, 1 = Info, 2 = Warning, 3 = Error, and 4 = Fatal. The default value is Warning.
Code Signing
sudo -u www-data php occ integrity:sign-app --privateKey=/home/thommie/github/oc-app-signing-netzwissen.de.key --certificate=/home/thommie/github/oc-app-signing-netzwissen.de.crt --path=/home/thommie/github/oc-theme-nw/
App Kommandos
app app:check-code check code to be compliant app:disable disable an app app:enable enable an app app:getpath Get an absolute path to the app directory (added in 9.0) app:list List all available apps
User Kommandos
Neuen User anlegen (displayname = voller Name, uid = Login)
sudo -u www-data php occ user:add --display-name 'Herr test1' --email 'support@netzwissen.de' --group 'User' test1 The user "test1" was created successfully Display name set to "Herr test1" Email address set to "support@netzwissen.de" User "test1" added to group "User"
Passwort als Umgebungsvariable übergeben (z.B. für Masseneintrag) - Achtung, geht nur als root
''export OC_PASS=newpassword ''''su -s /bin/sh www-data -c 'php occ user:add –password-from-env –display-name="Fred Jones" –group="users" fred' '' ''The user "fred" was created successfully Display name set to "Fred Jones" User "fred" added to group "users" ''
Passwort Reset
über cli
sudo -u www-data php occ user:resetpassword
über Mail
root@www:/var/www/owncloud# sudo -u www-data php occ user:resetpassword --send-email test1 The password reset link is: https://www.netzwissen.de/owncloud/index.php/lostpassword/reset/form/QgBwq9JIZJbdhXf7NLq7L/test1
über Link
sudo -u www-data php occ user:resetpassword --output-link test1
Letzten Login zeigen
sudo -u www-data php occ user:lastseen schreiber-esslingen@t-online.de
Inaktive User suchen
365 Tage
root@www:/var/www/owncloud# sudo -u www-data php occ user:inactive 365
User löschen
sudo -u www-data php occ user:delete
User temporär abschalten
user:disable [uid]
Einfacher Report über alle User
sudo -u www-data php occ user:report
Rescan aller Daten
sudo -u www-data php console.php files:scan –all
Dateien löschen, scannen, verschieben (bulk)
trashbin:cleanup Remove deleted files files files:cleanup cleanup filecache files:scan rescan filesystem files:transfer-ownership All files and folders are moved to another user - shares are moved as well. (Added in 9.0)
Datentransfer von User A nach User B:
sudo -u www-data php occ files:transfer-ownership --path="gruenerheiner" thommie4 gruenerheiner
Dateien landen beim neuen User in einem separatend transferred-.. Ordner
Verschlüsselung
sudo -u www-data php occ app:enable encryption sudo -u www-data php occ encryption:enable sudo -u www-data php occ encryption:status
Verschlüsselung & Sharing
Bei aktiver Verschlüsselung sollte immer über den Namen geshared werden, siehe https://doc.owncloud.org/server/master/user_manual/files/encrypting_files.html Erst danach sollte ein Gruppen Share gesetzt werden, der Namens-Share kann dann wieder weg.
Only users who have private encryption keys have access to shared encrypted files and folders. Users who have not yet created their private encryption keys will not have access to encrypted shared files; they will see folders and filenames, but will not be able to open or download the files. They will see a yellow warning banner that says “Encryption App is enabled but your keys are not initialized, please log-out and log-in again.”
Share owners may need to re-share files after encryption is enabled; users trying to access the share will see a message advising them to ask the share owner to re-share the file with them. For individual shares, un-share and re-share the file. For group shares, share with any individuals who can’t access the share. This updates the encryption, and then the share owner can remove the individual shares.
Datenbankschema
Libre Office Online (Collabora)
Anleitungen https://central.owncloud.org/t/howto-install-collabora-online-on-ubuntu-16-04-without-docker/3844/8
Wichtiger Hinweis von reto-ineichen (Jun 17):
Es geht auch viel einfacher, dank dem Team von Collabora CODE!
Gemäss https://www.collaboraoffice.com/code/ 61 z.B. für Ubuntu 16.04 LTS:
import the signing key
apt-key adv –keyserver keyserver.ubuntu.com –recv-keys 0C54D189F4BA284D
add the repository URL to /etc/apt/sources.list
echo 'deb https://collaboraoffice.com/repos/CollaboraOnline/CODE 28 ./' » /etc/apt/sources.list
perform the installation
apt-get update && apt-get install loolwsd code-brand
Dann kontrollieren, dass SSL-Zertifikate in /etc/loolwsd vorhanden sind, sonst wie folgt generieren (aus officeonline-install.sh), siehe https://github.com/husisusi/officeonlin-install.sh:
mkdir /etc/loolwsd\ openssl genrsa -out /etc/loolwsd/key.pem 4096\ openssl req -out /etc/loolwsd/cert.csr -key /etc/loolwsd/key.pem -new -sha256 -nodes -subj "/C=DE/OU=onlineoffice-install.com/CN=onlineoffice-install.com/emailAddress=nomail@nodo.com" openssl x509 -req -days 365 -in /etc/loolwsd/cert.csr -signkey /etc/loolwsd/key.pem -out /etc/loolwsd/cert.pem\ openssl x509 -req -days 365 -in /etc/loolwsd/cert.csr -signkey /etc/loolwsd/key.pem -out /etc/loolwsd/ca-chain.cert.pem
und dann noch gemäss Anleitung den Apache2-Proxy einrichten.
Der Vorteil liegt auch darin, dass ganz einfach zusätzliche Schriften in Collaboraonline kopiert werden können, nämlich in den Ordner /opt/collaboraoffice5.3/share/fonts/truetype. Danach muss nur noch mit
sudo systemctl restart loolwsd.service
loolwsd neu gestartet werden und alles klappt, wenn in OwnCloud/Nextcoud die App richtig aktiviert wurde.