You are reading an outdated version of this documentation. Please check out the latest version of the server administration manual.

JavaScript and CSS Asset Management

Warning

The asset pipelining feature has been remove in Nextcloud 10, because it broke several apps, calendar and gallery being two of them. In order to remove traces, you can manually remove the asset-pipeline.enabled and assetdirectory configs from your config file and delete the assets/ folder.

In production environments, JavaScript and CSS files should be delivered in a concatenated and compressed format.

Nextcloud can automatically collect all JavaScript and CSS files, aggregate and compress them to then save the result in a folder called ‘assets’ which can be found in the folder where Nextcloud has been installed.

If your Web server has write access to your Nextcloud installation, then the ‘assets’ folder will be automatically created for you, otherwise, you need to create it yourself before enabling that option and you must give write access to your Web server user.

Assets found in that folder will from now on be served as static files by your Web server and will be automatically refreshed whenever Nextcloud or one of its apps is updated. It’s important to note that apps installed via git might not always update their version number with every commit and this could lead to an out-of-sync asset folder. It is not recommended to enable asset-pipelining when using apps pulled via git.

Parameters

<?php
  $CONFIG = array (
    ...
    'asset-pipeline.enabled' => true,
    ...
  );

You can set this parameter in the config/config.php