@DeepDiver1975 please add snippets or links here

cc @davitol (who was looking for it)
cc @settermjd (the documentation magician)

owncloud/core#12601 (comment)

The \OCP\Contacts class contains several static methods: https://github.com/owncloud/core/blob/master/lib/public/Contacts.php

However the website doesn't show any of them: https://doc.owncloud.org/api/namespaces/OCP.Contacts.html

@DeepDiver1975 any idea how/when the doc generator script is run ?

The comfort of federated Sharing comes with a few side effects, such as potentially leaking email addresses with the sharer. This should be documented so the user can make an informed decision on whether or not he wants to disable this feature.

Apparently ocdev isn't maintained any more and has been removed from pip3, so the commands will not work any more.

Either we need to republish it to pip under another account or adjust the documented commands to be based on git.

As for the app generator, this is likely not replaceable so would need to remove it completely.

In an ideal world, either we need a new maintainer for ocdev or even better: rewrite the thing in PHP instead of Python...

What do you think ? @carlaschroder @DeepDiver1975 @butonic

I'm not even sure if hooks work as described on the hooks documentation page since almost nobody uses them that way, but one thing is for certain, documentation is missing regarding the requirements an app needs to have in order to be able to listen to filesystem hooks: the app needs to be of type filesystem, as described here: https://doc.owncloud.org/server/9.0/developer_manual/app/info.html#types

<?xml version="1.0"?>
<info>
....
    <types>
        <filesystem/>
    </types>
...
</info>

Import https://github.com/owncloud/administration/tree/master/config-sample-converter into this repo.

Find a way to run it regularily.

Maybe add a Makefile target to trigger it easily.

@settermjd

Hey @carlaschroder this will be released, around 1st June:

• ubuntu 16.04 support https://github.com/owncloud/ownbrander/issues/602
• Show the quota information for a different folder than the root https://github.com/owncloud/ownbrander/issues/593
• Server url hint https://github.com/owncloud/ownbrander/issues/587
• Enable/Disable sharing options https://github.com/owncloud/ownbrander/issues/580
• Fix partially the server url https://github.com/owncloud/ownbrander/issues/577
• Allow/don't modify proxie settings https://github.com/owncloud/ownbrander/issues/572
• Modify userID wording https://github.com/owncloud/ownbrander/issues/569

I am sorry, but after reading through the documentation, I am still confused, I am not sure among all the pages and links of documentation which “overrules” the other or how they are to be coordinated with each other, and therefore which I should be following in my case. Thank you in advance for helping to answer these questions.

1. I installed ownCloud 9.1.0 using the linux metapackage “owncloud” for Ubuntu 16.04. The instructions at https://doc.owncloud.org/server/9.1/admin_manual/installation/linux_installation.html seem to indicate that the way I manage updating is to allow my Ubuntu package manager take care of that. Is that correct?
2. At that same link above, it also says this: “Do not move the folders provided by these packages after the installation, as this will break updates.” The data I want the ownCloud server to make available will NOT be in /var/www/owncloud , instead, it will be in a different location. Will this be a problem for me? If so, what are my options?
3. Still at that same link above, it says this as a final step: “Follow the instructions on the download page to install ownCloud. Then run the Installation Wizard to complete your installation. (see Installation Wizard).” When I read the instructions for the “Installation Wizard” found at https://doc.owncloud.org/server/9.1/admin_manual/installation/installation_wizard.html , it says the first thing to do is to set strong directory permissions. So, does that mean that installing the Ubuntu metapackage “owncloud” does NOT set the correct permissions, and I need to go through this process of changing them?
4. At the link for the “Installation Wizard”, it says this about setting strong directory permissions: “These strong permissions prevent upgrading your ownCloud server; see Setting Permissions for Updating for a script to quickly change permissions to allow upgrading.” So, does this mean that after I install the Ubuntu metapackage “owncloud”, and after I have had to correct the directory permissions using the bash script, my Ubuntu package manager system/process will NOT work for doing updates because I’ve changed the directory permissions? And, does that mean that in order to do updates, I need to use the script to temporarily change the directory permissions? And, does that also mean that if my Ubuntu package manager cannot do updates, I will have to always update manually, even though the initial installation of ownCloud was via the use of the Ubuntu metapackage “owncloud”? Finally, doesn't this, by making my Ubuntu package manager unable to do updates, contradict what I thought was the case in my question #1 above? It just seems so contradictory to me that the instructions warn against moving the folders because that will "break updates" (see #2 above) - I am grateful for the warning! - but then later in the instructions it advises to change the permissions, along with a warning that such changes will break updates! I am so confused.....

@PVince81 as discussed on IRC

When trying to setup a development environment following https://github.com/owncloud/documentation/blob/master/developer_manual/general/devenv.rst
I ran into some issues. The most important issue was, that make did not finish sucessfully.

After digging I found the root cause on the failing make.

• It seems that the version from nodejs provided on Ubuntu 16.04 is out of date and does not meet the requirements. Currently nodejs version from the packte manager is on 4.2.6.
• Because I need to run make under sudo, make fails with bower because the parameter --allow-root is not set.

After removing npm and nodejs from the server, I installed
nodejs 7.x

curl -sL https://deb.nodesource.com/setup_7.x | sudo -E bash -
sudo apt-get install -y nodejs

sudo nodejs –v
v7.5.0
sudo npm –v
4.1.2

bower

sudo npm i -g bower

sudo bower -v
1.8.0

Now, after cloning you can run
sudo make

If you get an error at the end like bower ESUDO Cannot be run with sudo
finalize bower by running: sudo bower install --allow-root

Additional note on make:
I get the following reports. Should that be fixed?

Package guzzle/parser is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/common is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/stream is abandoned, you should avoid using it. Use guzzle/guzzle instead.
Package guzzle/http is abandoned, you should avoid using it. Use guzzle/guzzle instead.

The documentations says to chown directory data.
But this directory is not provided when cloning core and does not extists. You have to manually create it before.
Also, you need to chown the config directory, else setup does not work.

Related core PR: owncloud/core#27634

Whats new since OC10:

• Apps can define their own settings sections in addition to panels

Steps to do this:

• Add a <settings-sections> element in info.xml of the app. Sub element of <personal> or <admin> with the class name of the section. (See owncloud/core#27634)
• Create the relevant class, for example:

namespace OCA\MyApp;
use OCP\IL10N;
use OCP\Settings\ISection;
class AdminSection implements ISection {
	/** @var IL10N  */
	protected $l;
	public function __construct(IL10N $l) {
		$this->l = $l;
	}
	public function getPriority() {
		return 20;
	}
	public function getIconName() {
		return 'password';
	}
	public function getID() {
		return 'mycustomsection';
	}
	public function getName() {
		return $this->l->t('MyApp');
	}
}

Old PD-Menue has no step to configure a http proxy.
Check if new univention appliance has this!

Documentation should explain the manual steps in any case!

Content is the same. Why are there 2 URL's ?

@settermjd @pmaier1 @hodyroff @evirichard

Change this:
https://doc.owncloud.org/server/10.0/admin_manual/configuration_server/occ_command.html#encryption

and provide an example inside the data directory, ex: "data/allkeys".

An admin can first mount a separate volume to "data/allkeys" if they want the keys to be stored elsewhere.

Add warning that it's not supported to store keys outside of the data directory path.

@settermjd

Need to add the path "/heartbeat" to the paths that must NOT be redirected to the IDP here: https://doc.owncloud.org/server/8.2/admin_manual/enterprise_user_management/user_auth_shibboleth.html

In case of public upload, there is no other ajax request that would refresh the session. So if a public upload is running longer than the session timeout (or session.gc_maxlifetime), the heartbeat must be made to work to refresh the session. Failure to do so will have the ajax/upload.php call be rejected with "invalid token" because the request token will become invalid as it's stored in the session.
Note that ajax/upload.php uses POST, which means it only hits the OC code after PHP is finished receiving and storing the file to its temp folder, so the upload would not refresh the session until its very end, which is too late.

@DeepDiver1975 @butonic @felixboehm @pako81

1. Enterprise logging:
   https://doc.owncloud.com/server/9.1/admin_manual/enterprise_logging/enterprise_logging_apps.html
   needs to include all logged events => https://github.com/owncloud/enterprise/blob/master/admin_audit/appinfo/info.xml

2. Comparison of logging features between CE and EE

ownCloud Server (Community Version)

• System-Fehler-Logging (PHP-Fehler, DAV-Fehler, fehlgeschlagene Login-Versuche)
  z.B.: “Login failed: 'user1' (Remote IP: 'x.x.x.x') 2017-01-18T13:59:36+00:00”
  https://doc.owncloud.com/server/9.1/admin_manual/configuration_server/logging_configura
  tion.html
• Community Apps Fehler-Logging (z.B. Mailserver oder externe Storages falsch
  konfiguriert)
  → Tools zur Analyse und Behebung von Systemfehlern oder Fehlkonfigurationen

ownCloud Enterprise Edition

• System-Fehler-Logging (wie Community Version)
• Community Apps Fehler-Logging (wie Community Version)
• Auditing-Modul:
  → Protokollierung von
  • Logins/Logouts von Nutzern
  • Dateisystem-Operationen von Nutzern (z.B. Dateien erstellen/loeschen/verschieben, Papierkorb)
  • Sharing-Operationen von Nutzern (z.B. internes Sharing, Sharing via Link, Setzen/aendern von Berechtigungen, Aufrufe der Sharing API durch Clients)
  • Setzen/loeschen von Datei-Tags von Nutzern
  • Nutzer-Management-Operationen (z.B. User anlegen/loeschen, User aktivieren/deaktivieren)
• Enterprise Apps Logging (z.B. File Firewall)
  • separate App-Logs (z.B. durch File Firewall verhinderte Zugriffe)

Empfehlungen
ownCloud Logfiles werden im Syslog-Format abgelegt. Diese sind über die Admin-Oberfläche
sowie über das standardmaessig aktivierte Einbinden des lokalen Speichers (Externe Storages -> Lokal) für den ownCloud Administrator lesbar.
Wir empfehlen die Logfiles direkt über für Linux verfügbare Open Source Tools zu schreiben
und dann dort auszuwerten. Dabei kann ein kontrollierter Zugriff (mehrere Admins, Betriebs-/Personalrat, etc.) definiert werden und sinnvolle Auswertungen für den Support zur
Verfügung gestellt werden.

Need English translation? Questions?

Docs already cover protection for SSH logins: owncloud-archive/documentation#2936

It's also very useful, to block failed ownCloud logins. To achieve this, fail2ban can "read" the owncloud.log.

Community documented it in the forums for the older versions:
https://central.owncloud.org/t/fail2ban-and-owncloud-8-x-9-0-x/837

It seems log format changed with oC 10:
https://central.owncloud.org/t/owncloud-10-0-0-will-change-the-owncloud-log-format-a-bit/6837

In this discussion, an awesome person provided a working config in the last post:
https://central.owncloud.org/t/fail2ban-and-oc-10/7776

@jvillafanez Would you recommend this?

[Definition]
failregex={"reqId":".*","level":2,"time":".*","remoteAddr":".*","user":".*","app":"core","method":"POST","url":".*","message":"Login failed: '.*' \(Remote IP: '<HOST>'\)"}

@pmaier1 Log format shouldn't change again, but if it does, the change needs to be documented in the docs. /cc @settermjd

Regarding the feature to select either master key or user specific key encryption implemented here: owncloud/core#27512 needs documentation.

https://github.com/cernbox/smashbox/blob/master/protocol/protocol.md

@DeepDiver1975 can you take care of it or at least give guidelines to @settermjd about what/how to document it ?

CC @butonic

The data-fingerprint is added in owncloud/core#24054. More details in https://github.com/owncloud/enterprise/issues/966.

Basically it is a property to let the clients find out if a backup has been restored.
We should probabaly have generic restore-backup docs and what to do.

CC: @carlaschroder

• Folder or file with a space at the end (trailing spaces) (owncloud/core#28164)
• .htaccess (config/config.sample.php)
• *.part files (owncloud/core#7496)
• too long filenames (owncloud/core#25425, perhaps fixed soon?)
• client/sync-exclude.lst
• handling cases (owncloud/core#17161, owncloud/client#1348)
• Desktop.ini in root (2.4+) (src/csync/csync_exclude.cpp#L324-L329, owncloud/client#6200)
• Files with leading dot (example .12345.pdf) are handled as hidden files on all plattforms. (user need to activate "sync hidden files" to sync them)
• … what else ?

@settermjd Where can this be located?

Previously documented:

• https://github.com/owncloud/core/wiki/Cross-Platform-File-Handling
• https://doc.owncloud.org/desktop/architecture.html#ignored-files-label

/cc @pmaier1 @hodyroff

In regards to the procedure for publishing a new branded iOS app, our documentation is still pointing to the use of xcarchive:

https://doc.owncloud.com/branded_clients/branded_ios_app/publishing_ios_app_9.html

This is however an obsolete procedure, since xcode-> application loader should instead be used as @michaelstingl explained me. We would need therefore to update our doc accordingly.
@settermjd thanks.

Workflow engine is only available in EE, so this would belong to the EE parts of the docs.

Here is an example app https://github.com/nickv-oc/workflow_doctopdf

Ref original ticket for workflow: https://github.com/owncloud/workflow/issues/81

@settermjd

CC @hodyroff

https://doc.owncloud.org/server/9.0/admin_manual/maintenance/upgrade.html

From the document:

How to Upgrade Your ownCloud Server
There are three ways to upgrade your ownCloud server:
Using your Linux package manager with our official ownCloud repositories. This is the recommended method.

As far as I know, we don't recommend using the repositories, do we?

This is the place to discuss improvements to the Deployment Recommendations document (master copy here https://github.com/owncloud/documentation/blob/master/admin_manual/installation/deployment_recommendations.rst ).

@plastikschnitzer posted some good questions in owncloud-archive/documentation@498fe74:

Hi,
you write in the deployment manual about 3 examples of server setups:
Small: up to 150 users with a single server setup
Medium: 150-1000 users with a multi-server setup
Big: 5000 - 100000 users with a bigger multi-server setup

My questions:

1. On which user behavior and file sizes are these recommendations based on?
2. How many desktop clients/webbrowser/mobile apps do you calculate per user?
3. Are all users online at the same time or are they spread around the world and work in different timezones?
4. Are these recommendations for the default OC-code and default template or are some tweaks included?

I think there is a lot you can tweak, for example gzip compression, asset pipelining, browser caching, removing @font-face. This way, I could reduce the weight of the login page from 1,68 MB and 72 server requests down to 265 kB and 8 server requests. Have possible tweaks like this taken into considerations for recommended server setups?

Three new entries in info.xml can be used to execute repair steps:

• Before database migration
• After database migration
• As a background job to be executed asynchronously after migration, in live operations
• Install and uninstall steps

I submitted my first contribution here a while back (owncloud-archive/documentation#2185) and found some minor styling issues and things frequently in the docs. I noticed that in a few places the links are invalid or style issues exist.

I think it'd be a great idea to add a static analysis tool to check rst formatting for the documentation.
In specific, I was thinking of coala (https://github.com/coala-analyzer/coala). I've been contributing to the project for a while - and a neat checker for "Invalid Links" was created recently to check their docs.

I think the following would be good value-adds (from the top of my head):

• InvalidLinks - Checks for invalid links (links that are broken or give 40x, 50x) in the rst files
• restLinter - To check rst syntax
• LanguageTool - To check grammar issues
• SpaceConsistency - To check for unnecessary white space and newlines

Also, there's a CI gitmate associated with it which directly comments with patches in github PRs - which is under beta. In case you do not want to use jenkins, travis, circleci, etc

Is this something that you'll would like to pursue ?
I could help set it up.

Edit: Note that it has the capability to auto apply patches when feasible

1. Favorite some files in the web UI
2. Create a file "report-favorite.xml" with the following contents

<?xml version="1.0" encoding="utf-8" ?>
<oc:filter-files xmlns:a="DAV:" xmlns:oc="http://owncloud.org/ns" >
        <a:prop>
                <!-- add Webdav properties to query here, like for PROPFIND -->
                <a:getetag/>
                <a:resourcetype/>
                <a:getcontentlength/>
        </a:prop>
        <!-- required filter rules, at least one needs to be specified -->
        <oc:filter-rules>
                <!-- add filter rules here -->
                <oc:favorite>1</oc:favorite>
        </oc:filter-rules>
        <!-- optional search block for pagination -->
        <oc:search>
                <!-- offset to retrieve (here 200 would be page 2) -->
                <oc:offset>200</oc:offset>
                <!-- number of results to retrieve -->
                <oc:limit>100</oc:limit>
        </oc:search>
</oc:filter-files>

1. curl -u admin:admin -X REPORT -H "Content-Type: text/xml" --data-binary "@report-favorite.xml" 'http://localhost/owncloud/remote.php/dav/files/admin/'

This will return a multistatus result containing all favorite files from any subdirectory:

<?xml version="1.0"?>
<d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:cal="urn:ietf:params:xml:ns:caldav" xmlns:cs="http://calendarserver.org/ns/" xmlns:card="urn:ietf:params:xml:ns:carddav" xmlns:oc="http://owncloud.org/ns">
  <d:response>
    <d:href>/owncloud/remote.php/dav/files/admin/welcome.txt</d:href>
    <d:propstat>
      <d:prop>
        <d:getetag>"e974c6a3c7d8886158b2911ab6cc7fea"</d:getetag>
        <d:resourcetype/>
        <d:getcontentlength>163</d:getcontentlength>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
  </d:response>
  <d:response>
    <d:href>/owncloud/remote.php/dav/files/admin/sub/another</d:href>
    <d:propstat>
      <d:prop>
        <d:getetag>"58d2b5c6912da"</d:getetag>
        <d:resourcetype>
          <d:collection/>
        </d:resourcetype>
      </d:prop>
      <d:status>HTTP/1.1 200 OK</d:status>
    </d:propstat>
    <d:propstat>
      <d:prop>
        <d:getcontentlength/>
      </d:prop>
      <d:status>HTTP/1.1 404 Not Found</d:status>
    </d:propstat>
  </d:response>
</d:multistatus>

It only returns the required properties just like PROPFIND.

I stumbled over https://labs.ig.com/logging-level-wrong-abstraction. The introduction appealed to me because I am reading too many OC logfiles, anyway. I keep finding myself ignoring useless lines and craving for the debug log quite often, so I propose we give app developers a recommendation which log level to use:

DEBUG: information that is useful during development. Usually very chatty, and will not show in production.
INFO: information you will need to debug production issues.
WARN: someone in the team will have to investigate what happened, but it can wait until tomorrow.
ERROR: Oh-oh, call the fireman! This needs to be investigated now!

Or as the blog post put it:

With this usage in mind, the log level question becomes: “Do I want to wake up in the middle of the night to investigate this, or can it wait until tomorrow morning?”, which is very concrete and a question that even your Business Manager/Production Owner should be able to answer.

In our doc I only found the debug levels in tha admin manual. https://github.com/owncloud/documentation/blob/master/admin_manual/configuration_server/logging_configuration.rst

We should add the above guido to the developer guide.

In order to avoid misunderstanding between the meaning of favorite on the web gui and on the mobile apps we have changed the feature name to "available offline" plus we have updated the icons so that they are pretty similar (indeed, they are based on) the desktop client, 1 platform goal!

Android work on: owncloud/android#1218

(iOS will follow)

The UI and flow has changed so might need to update screenshots.

@settermjd please try it out, let me know if you need help to set it up.

This latest release of the ownBrander includes a new branding option within the desktop client; Update of server url. This option is expected to be used only if you want to modify the server url to which your customers will connect from one desktop version to the following one.

@settermjd

owncloud/core#24771

We improved the way people can add a public link share to their ownCloud. You no longer add the URL of your ownCloud to the "add to your ownCloud field", instead you enter your federated cloud id. The owner will then send you a federated cloud share and you will be re-directed to your ownCloud. After login you will get the notification about a new federated share and can accept/decline it.

This way the owner sees in the share dialog every mounted public link as a seperated share, can change the permissions, unshare it, etc.

See owncloud/core#18316 for an example

cc @BernhardPosselt @oparoz @PVince81 @LukasReschke @nickvergessen

Define process for documentation

If things need documentation, what to do?

• open issue in this repo
• search for label "documentation" through all ownCloud repos:
  https://github.com/issues?utf8=%E2%9C%93&q=is%3Aopen+is%3Aissue+user%3Aowncloud+sort%3Aupdated-desc+label%3Adocumentation
• mention team: @owncloud/doc

Documentation Documentation

Where to put the documentation for the documentation?

• https://github.com/owncloud/documentation/wiki
• https://github.com/owncloud/documentation/blob/master/GETTING_STARTED.rst
• https://doc.owncloud.com/server/9.2/developer_manual/

Planning for documentation - The Documentation Roadmap

Where do we plan and set priorites our documentation work?

• Create a Project? https://github.com/owncloud/documentation/projects

More options?? Ideas?

After https://doc.owncloud.org/server/9.1/admin_manual/installation/source_installation.html#additional-apache-configurations add a section on how to make apache log json. Rationale: structured data is perfect for machine readable log files.

LogFormat "{\"reqId\":\"%{UNIQUE_ID}e\",\"time\":\"%{%Y-%m-%dT%H:%M:%S%z}t\",\"remoteAddr\":\"%a\",\"user\":\"%u\",\"host\":\"%V\",\"method\":\"%m\",\"request\":\"%U\",\"query\":\"%q\",\"status\":%>s,\"userAgent\":\"%{User-agent}i\",\"referer\":\"%{Referer}i\",\"duration\":%D}" jsonlog

CustomLog /var/log/apache2/access_log jsonlog

• UIQUE_ID is optional, see https://github.com/owncloud/documentation/issues/2967
• we could also ad bytes received and bytes sent? Requires mod_logio

LogFormat "{\"reqId\":\"%{UNIQUE_ID}e\",\"time\":\"%{%Y-%m-%dT%H:%M:%S%z}t\",\"remoteAddr\":\"%a\",\"user\":\"%u\",\"host\":\"%V\",\"method\":\"%m\",\"request\":\"%U\",\"query\":\"%q\",\"status\":%>s,\"userAgent\":\"%{User-agent}i\",\"referer\":\"%{Referer}i\",\"duration\":%D,\"bytesReceived\":%I,\"bytesSent\":%O,\"pid\":%P,\"keepAlive\":%k,\"conStatus\":\"%X\"}" jsonlog

CustomLog /var/log/apache2/access_log jsonlog

• maybe if we target ELK this makes more sense: http://untergeek.com/2012/10/11/getting-apache-to-output-json-for-logstash/ but we need to ask someone with logstash know how

https://github.com/owncloud/enterprise/issues/1464

The documentation currently tells a developer what they need to do and what standards they need to maintain to get an app published in the app store. However, it does not give any guidence on how to go about publishing an app.

There should be a step-by-step guide somewhere that covers at least the following.

• What are the mechanics of the process?
• How to upload code?
• Some apps can be updated by clicking a button in the apps page of OC, does this require special code, or is it automatic?
• Signing apps

Somebody with a better understanding of the process could probably come up with a better list.

On https://doc.owncloud.org/server/9.1/admin_manual/configuration_server/logging_configuration.html we should

• add a dedicated section on how to install mod_unique_id and and changin the log format to add the unique_id. If the UNIQUE_ID environment variable is present OC will also use it for the owncloud log file, which allows matching log entries from apache to oc and vice versa.

• recommend the mod_user_id module for apache in https://doc.owncloud.org/server/9.1/admin_manual/installation/source_installation.html#apache-web-server-configuration with a link to the new section in the logging config

• Thanks to this new option users may be able to delete all the local files within the current account
• Important, favorite files won't be deleted by definition these files are available and updated within the device
  owncloud/ios-legacy#640 (comment)
• Besides in this issue we have changed the way the account is deleted, the goal is to make it simpler since it was an option not easy to find, right now we are taking advantage of the 3 dots menu

This is meta-issue for the auth related changes we need to document.

In 9.1 we added the following features:

• Ability to track/list/kill browser sessions -> owncloud-archive/documentation#2479
• Ability to create/kill device specific passwords -> owncloud-archive/documentation#2479
• Password changes log out connected browsers/devices automatically
• Clients use the device specific password either as password for basic auth or use a new header -> owncloud-archive/documentation#2479
• Admins can enforce clients to authenticate with app specific passwords (login password is blocked then) -> documented via the sample config
• Two-factor auth (which also enforces app specific passwords for devices) -> owncloud-archive/documentation#2479

I can open separate issues with more details next week.

Extension point is defined as follows:

    var MyClass = function() {
        // attach plugins to this instance
        OC.Plugins.attach('OC.MyApp.MyExtensionPointName', this);
    };
    MyClass.prototype = function() {
        someMethod: function(abc) {
            return "Some text " + abc;
        }
    }

Plugins can register themselves to this extension point using this:

    OC.Plugins.register('OC.MyApp.MyExtensionPointName', {
        // the plugin receives the MyClass instance as argument since it was passed in the extension point call
        attach: function(object) {
            // extend method "someMethod"
            var oldMethod = object.someMethod;
            object.someMethod = function(abc) {
                // call old method to keep old functionality
               var result = oldMethod.apply(this, arguments);
               // do something additionally, for example append something to the result
               result = result + ' (something appended)';
               // for example set an attribute
               object._attributeFromPlugin = true;
               // pass old value back
               return result;
            }
        }   
    });

Primary object store mode and external storage mode use a different storage format.

The external storage variant stores the file in a tree-like manner, so the object keys are like:

• "somedir/"
• "somedir/somefile.txt" + contents of file as data
• "somedir/anotherfile.txt" + contents of file as data

But this has the drawback that it's bad for performance because it is difficult to propagate etags/mtimes etc manually while simulating a file tree structure.

The purpose of the primary object storage is to use another more efficient approach were basically the object keys are only the file ids from oc_filecache, so looking at its contents you'd see:

• 15 with the contents of "somefile.txt"
• 20 with the contents of "test.txt"

and if you look at entry with fileid 15 in filecache you'd see the "somedir/somefile.txt" entry.

So switching from external storage to primary storage will not work because the format of the keys is not the same.

see: owncloud/core#18716

During upload a new header OC-Checksum can be provided which will tell the server to store this checksum. This checksum can then later be obtained via propfind and will be returned when downloading the file.

Currently the checksum is just stored. No server side verifiation or generation is done.

Core and app updates are checked every 24h via a background job.

Via the notifications API the update notification is then also available in the sync client and therefor helps people to remember to update their instances, even though they never check the web
UI.

The admin can pick a custom group of users to notify for updates. This is useful for “secure installations” where no syncing user is an admin.
Restriction:

• Core update notification is only available for update channels: beta, stable and production
• App updates are checked against the app store only

@carlaschroder

There are many reasons why it might look like the sync client is not syncing.
Collection of known reasons and checks will help users to resolve their issues.

• Sync client running?
• Check internet connection?
• Sync is paused?
• Files / folders not selected to sync in selective sync settings?
• Can you access the files in the web browser?
• If a new file / folder is not synced to your laptop
  • check if your local disc has sufficient free disc space
  • check if the download limit is hit, and acknowledge to sync files in the selective sync view
• Are there conflict files?
• Are the files changed on an external storage (windows network drive mount) on the server?
• Missing file listed in Activities tab in list "not synched"?
• Are there error messages? Press F12 to find detailed infos in the sync client log

not complete ...

Was already asked twice on IRC:

Examples are in this PR: owncloud/core#21858

This was always a bit obscure.
There was a day where I wrote smashbox tests and had to figure them all out.

They are currently documented inline in the code: https://github.com/owncloud/smashbox/blob/master/lib/oc-tests/test_sharePermissions.py#L43.

I've taken them out and put them below for better readability:

Permissions masks:

• READ = 1
• UPDATE = 2 ("can update" in web UI)
• CREATE = 4 ("can create" in web UI)
• DELETE = 8 ("can delete" in web UI)
• SHARE = 16 ("can reshare" in web UI)

File operations shorthand for the later table:

• download: download/read/get a file or display a folder contents
• upload: a new file can be uploaded/created (file target does not exist)
• upload_overwrite: a file can overwrite an existing one
• rename: rename file to new name, all within the shared folder
• move_in: move a file from outside the shared folder into the shared folder
• move_in_overwrite: move a file from outside the shared folder and overwrite a file inside the shared folder (note: SabreDAV automatically deletes the target file first before moving, so requires DELETE permission too)
• move_in_subdir: move a file already in the shared folder into a subdir within the shared folder
• move_in_subdir_overwrite: move a file already in the shared folder into a subdir within the shared folder and overwrite an existing file there
• move_out: move a file to outside of the shared folder
• move_out_subdir: move a file out of a subdir of the shared folder into the shared folder
• copy_in: copy a file from outside the shared folder into the shared folder
• copy_in_overwrite: copy a file from outside the shared folder and overwrite a file inside the shared folder (note: SabreDAV automatically deletes the target file first before copying, so requires DELETE permission too)
• delete: delete a file inside the shared folder
• mkdir: create folder inside the shared folder
• rmdir: delete folder inside the shared folder

The following lists what operations are allowed for the different permission combinations (share permission is omitted as it is not relevant to file operations):

• READ (aka read-only):

  • download

• READ + CREATE:

  • download
  • upload
  • move_in
  • copy_in
  • mkdir

• READ + UPDATE:

  • download
  • upload_overwrite
  • rename

• READ + DELETE:

  • download
  • move_out
  • delete
  • rmdir

• READ + CREATE + UPDATE:

  • download
  • upload
  • upload_overwrite
  • rename
  • move_in
  • copy_in
  • mkdir

• READ + CREATE + DELETE:

  • download
  • upload
  • move_in
  • move_in_overwrite
  • move_in_subdir
  • move_in_subdir_overwrite
  • move_out
  • move_out_subdir
  • copy_in
  • copy_in_overwrite
  • delete
  • mkdir
  • rmdir

• READ + UPDATE + DELETE

  • download
  • upload_overwrite
  • rename
  • move_out
  • delete
  • rmdir

• READ + CREATE + UPDATE + DELETE (all permissions):

  • download
  • upload
  • upload_overwrite
  • rename
  • move_in
  • move_in_overwrite
  • move_in_subdir
  • move_in_subdir_overwrite
  • move_out
  • move_out_subdir
  • copy_in
  • copy_in_overwrite
  • delete
  • mkdir
  • rmdir

Regarding the default_language setting I think that the text on https://github.com/owncloud/documentation/blob/master/admin_manual/configuration_server/language_configuration.rst

Please check settings/languageCodes.php for the list of supported language codes.

is wrong, as in this file https://github.com/owncloud/core/blob/master/settings/languageCodes.php , for example "de" is missing.

It should be corrected, as far as i understand, the list of available languages is now the list of files in oc/settings/l10n. Please correct me, if I am wrong.

Additional question: what are the language codes for "Deutsch (Persönlich)" und "Deutsch (Sie-Form)" ? Are these "de" respectively "de_DE" ?