How to force automatic removal of deleted files in nextcloud

Transcription

1 How to force automatic removal of deleted files in nextcloud Nextcloud will get rid of files that have been deleted for 30 days. However in reality these files will remain on the server until such a time that physical storage is running low. In other words they deleted items don t actually get deleted until necessary! In the third installment of optimizing nextcloud performance, we will tweak the default settings for automatically deleting files. Configuration parameters Config parameters exist to allow nextcloud server owners the capability of adapting this behavior, these are as follows: auto standard behavior D, auto change the minimum days a file is kept with standard behavior auto, D delete after a number of days, but earlier if space is required D1, D2 do not delete before, but definitely delete after a certain number of days disabled disable automatic deletion

2 Example rules To automatically delete files after 30 days, and give nextcloud the ability to delete sooner if space does eventually run low, you can add this to your config.php file located at /var/www/html/nextcloud/config/config.php you would add the following: 'trashbin_retention_obligation' => 'auto, 30', To ensure all files are retained for 30 days, but definitely deleted after 35 days, the following can be added to your config.php: 'trashbin_retention_obligation' => '30, 35', How to install Fulltextsearch in Nextcloud with Elasticsearch and Tesseract OCR

3 In the second of a series of tutorials on enhancing nextcloud performance and functionality, we are going to implement full text search with Elasticsearch and Tesseract OCR. This tutorial has been tested on nextcloud 13, 14 and 15 however the Tesseract OCR extension is not available for nextcloud 15 yet. Prerequisites Please ensure that the following plugins have been installed on your nextcloud server instance. Full text search Bookmarks Full text search Elasticsearch Platform Full text search Files Tesseract OCR Full text search Files Full text search Install Elasticsearch

4 Elasticsearch is a java based application so we will need to install open JDK. This can be installed by running the following command: # sudo apt-get install openjdk-8-jre Once installed we can now add the Elasticsearch repository with: # sudo apt install apt-transport-https # wget -qo - sudo aptkey add - # echo "deb stable main" sudo tee -a /etc/apt/sources.list.d/elasticsearch.list # sudo apt update Once the repository has been added we can now go ahead and install Elasticsearch: # sudo apt install elasticsearch In this instance we are going to bind Elasticsearch to the localhost which is by running the following command: # sudo nano /etc/elasticsearch/elasticsearch.yml And edit or add the following line:

5 # network.host: To reload the configuration file and enable the service we will need to run the following command: #sudo systemctl daemon-reload && sudo systemctl enable elasticsearch && sudo systemctl start elasticsearch To check that the Elasticserver is running, enter the following: # curl -XGET ' :9200/?pretty' All things going well you should see an output something like this: Once we have verified that Elasticsearch is running we now need to install the ingest-attachment plugin which is required

6 to facilitate searches with the file extensions of.pdf,.ppt,.xls etc: # sudo /usr/share/elasticsearch/bin/elasticsearch-plugin install ingest-attachment Finally, restart Elasticsearch with: # sudo systemctl restart elasticsearch Install Tesseract OCR Install Tesseract OCR with the following command: # sudo apt install tesseract-ocr Next we will install additional languages. In this example English, German and French. If you require specific language packs go to for reference: # sudo apt install tesseract-ocr-eng tesseract-ocr-deu tesseract-ocr-fra If you wish to install all available language packs then use the following command:

7 # sudo apt install tesseract-ocr-all Configure nextcloud Now that Elasticsearch and Tesseract are both installed, we can now configure nextcloud. Go to Administration > Full Text Search and adjust the following settings as illustrated below: Use these settings to configure Elasticsearch on nextcloud.

8 Create the index Assuming you have installed and configured nextcloud via the tutorials on this site then then to create the index we have to run the following command in our nextcloud-directory: # sudo -u www-data php /var/www/html/nextcloud/occ fulltextsearch:index

9 You should then see the following in terminal: The first run of indexing may take time but once completed you can test Elasticsearch as illustrated below:

10 You have now successfully implemented full text searching on your cloud server. Enable caching in nextcloud server This is the first of a series of tutorials to improve the

11 performance and security of your nextcloud server installation. In this tutorial we shall install ACPu and Redis on an existing nextcloud server. Over time, as your nextcloud file and folders increase in size, your server performance will begin to slow. To counter this we can implement caching which will assist by maintaining the performance and speed for your server. ACPu will handle a lot of the caching initially, leaving Redis to manage file locking. As the server content grows and ACPu demands more resources, we will configure Redis to handle distributed caching. Stop Apache server in order to install ACPu and Redis we will need to stop Apache server with the following. # sudo service apache2 stop Install and configure ACPu and Redis To install all the required software, run the following command.

12 # sudo apt install php-apcu redis-server php-redis Once installed we shall start of by editing the Redis configuration file /etc/redis/redis.conf. This is achieved by running the following command. # sudo nano etc/redis/redis.conf Now find port 6379 and change it to 0. Then uncomment the following. unixsocket /var/run/redis/redis.sock Look for and change the permissions from 700 to 770 in the unixsocketperm directive as illustrated below. unixsocketperm 700 Save the file with ctrl & x We now need to add the Apache user www-data to the Redis group with the following. # sudo usermod -a -G redis www-data Finally restart Apache server with.

13 # sudo service apache2 restart And start the Redis service with. # sudo service redis-server start Now that Redis is installed and configured we now need to add the caching configuration to the nextcloud configuration file located at /var/www/html/nextcloud/config/config.php # sudo nano /var/www/html/nextcloud/config/config.php Then add the following piece of code to the config file. 'memcache.local' => '\\OC\\Memcache\\Redis', 'memcache.locking' => '\\OC\\Memcache\\Redis', 'filelocking.enabled' => 'true', 'redis' => array ( 'host' => '/var/run/redis/redis.sock', 'port' => 0, 'timeout' => 0.0, ), The server will have to be restarted for the changes to take effect but before we do that we will need to make sure that the Redis server is enabled to start on boot with. # sudo systemctl enable redis-server

14 Restart the server and caching will now be running. How to fix file upload errors in WordPress Have you ever tried to upload a file on wordpress only to see the following error message: The uploaded file exceeds the upload_max_filesize directive in php.ini WordPress has certain size limits depending on the platform that s hosting your WordPress site. In turn, the PHP memory that is designated for plugins, themes and scripts also have a certain cap. Like most error messages that flash up on computer screens and scare the living daylights out of everyday users the fix to the problem is relatively easy and there are several options to resolve this that focus on upload_max_filesize.

15 Option 1: edit.htaccess To begin with navigate to the root directory of WordPress. If you are using a hosted platform then you should be able to navigate to the root directory using a file manager or ftp. If, like me you are self hosting, then you will need to edit the.htaccess file via CLI Add the following line at the bottom of the.htaccess file. php_value upload_max_filesize 256M Save the file and leave it for a few minutes then try uploading the file again. If you are self hosting then you can simply restart the server to implement the changes. If the problem persists you could try increasing the limits on the following directives. php_value post_max_size 256M php_value memory_limit 512M php_value max_input_time 180 php_value max_execution_time 180 If these changes do not resolve the issue then consider option 2. Option 2: Edit wp-config.php This file is located in the main WordPress directory. Open the

16 file and add the following directive before the /* That s all, stop editing! Happy Blogging. '256M' ); Option 3: Update the php.ini file If you look closely at the upload_max_filesize error, you may have worked out that it has something to do with the php.ini which is a file that sets the php limit related variables. In most cases if you are using a hosting service, these limits will be set to their maximum values for convenience therefore you won t be able to change these settings. However if you are self hosting then you should be able to edit this. You will have to navigate to the php.ini file location which will vary depending on your setup. In my case the php.ini file is located at: /usr/local/etc/php.ini Open the file and look for the upload_max_filesize directive and increase it. You may also want to consider increasing the some other directives to see if they will resolve the issue. upload_max_filesize = 256MB post_max_size = 256M memory_limit = 512M max_execution_time = 180

17 Option 4: Contact Support If all of the options outlined above do not resolve the issue and you are on a hosted platform then you should consider contacting your hosts customer support. Do tell them what steps you have taken to try and resolve the issue. You may also want to take a look at the current upload limit which can be found via Media/Add New as illustrated below. Navigate to Media/Add New to view the maximum file upload limit Conclusion In this tutorial we have looked at 4 different options that can be taken to resolve the The uploaded file exceeds the upload_max_filesize directive in php.ini Solving Bluetooth issues in

18 Linux As with any new release of software, a few bugs have come to the surface with the release of Ubuntu This particular bug affects affects bluetooth connectivity. Basically the version of bluez which shipped with Ubuntu was noted to be a bit buggy, however an update has been release which should resolve the issue and can be obtained from the following PPA sudo add-apt-repository ppa:bluetooth/bluez sudo apt-get update Please note that this PPA is untrusted. You can browse to the original site via this link