Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

--- dienste:bytecluster0002:cloud [21.02.2021 11:56] – angelegt mape2k
+++ dienste:bytecluster0002:cloud [07.03.2025 23:54] (aktuell) – Update config for Nextcloud mape2k
@@ Zeile 1: / Zeile 1: @@
-====== Container 'wordpress-technikkultur' ======
+====== Container 'cloud' ======
 ===== Ressourcen =====
@@ Zeile 5: / Zeile 5: @@
   * 2 Cores
   * 5 GB HDD (root-fs)
-  * 35 GB HDD (data)
+  * 40 GB HDD (/var/www)
 ===== System =====
@@ Zeile 16: / Zeile 16: @@
   * Nextcloud (via NGINX)
+===== Betrieb =====
+==== Nextcloud aktualisieren (auf der Konsole) ====
+  - Updater ausführen
+    * **sudo -u www-data php /var/www/public_html/updater/updater.phar**
+      * Start update? [y/N] **y**
+      * Should the "occ upgrade" command be executed? [Y/n] **y**
+      * Keep maintenance mode active? [y/N] **n**
+  - In Nextcloud einloggen und unter [[https://cloud.technikkultur-erfurt.de/settings/admin/overview|Einstellungen - Verwaltung - Übersicht]] prüfen. Folgende Fehler sind "normal":
+    * Dein Web-Server ist nicht richtig eingerichtet um "/.well-known/caldav" aufzulösen.
+    * Dein Web-Server ist nicht richtig eingerichtet um "/.well-known/carddav" aufzulösen.
+    * Es wurde kein PHP-Memory-Cache konfiguriert.
+  - Angezeigte Fehler prüfen und korrigieren
+    - Nutzung von OCC: **sudo -u www-data /var/www/public_html/occ ...**
+==== Backup  ====
+  Dateien per Shell sichern
+    - cd /var/www/public_html
+    - sudo -u www-data php occ maintenance:mode --on
+    - sudo tar -cpzf //nc_backup_`date +"%Y%m%d"`.tar.gz -C /var/www/public_html/ .
 ===== Installation =====
@@ Zeile 24: / Zeile 46: @@
   - NGINX und PHP-FPM installieren
-    * **sudo apt-get install php7.3 php7.3-cli php7.3-fpm php7.3-curl php7.3-gd php7.3-json php7.3-xml php7.3-mbstring php7.3-zip php7.3-mysql php7.3-bz2 php7.3-intl php7.3-bcmath php7.3-gmp php-imagick nginx**
+    * **sudo apt-get install php8.2 php8.2-cli php8.2-fpm php8.2-curl php8.2-gd php8.2-xml php8.2-mbstring php8.2-zip php8.2-mysql php8.2-bz2 php8.2-intl php8.2-bcmath php8.2-gmp php-imagick libmagickcore-6.q16-6-extra nginx**
   - Default-Konfiguration anpassen<file|/etc/nginx/sites-available/default>
 server {
@@ Zeile 55: / Zeile 77: @@
         add_header X-Frame-Options                      "SAMEORIGIN"    always;
         add_header X-Permitted-Cross-Domain-Policies    "none"          always;
-        add_header X-Robots-Tag                         "none"          always;
+        add_header X-Robots-Tag                         "noindex,nofollow"          always;
         add_header X-XSS-Protection                     "1; mode=block" always;
@@ Zeile 91: / Zeile 113: @@
             try_files $uri $uri/ =404;
         }
+        # Add mime tye
+        types {
+            application/javascript mjs;
+        }
+        # Rule borrowed from `.htaccess` to handle Microsoft DAV clients
+        location = / {
+            if ( $http_user_agent ~ ^DavClnt ) {
+                return 302 /remote.php/webdav/$is_args$args;
+            }
+        }
+        location = /robots.txt {
+            allow all;
+            log_not_found off;
+            access_log off;
+        }
+        # Make a regex exception for `/.well-known` so that clients can still
+        # access it despite the existence of the regex rule
+        # `location ~ /(\.|autotest|...)` which would otherwise handle requests
+        # for `/.well-known`.
+        location ^~ /.well-known {
+            # The rules in this block are an adaptation of the rules
+            # in `.htaccess` that concern `/.well-known`.
+            location = /.well-known/carddav { return 301 /remote.php/dav/; }
+            location = /.well-known/caldav  { return 301 /remote.php/dav/; }
+            location /.well-known/acme-challenge    { try_files $uri $uri/ =404; }
+            location /.well-known/pki-validation    { try_files $uri $uri/ =404; }
+            # Let Nextcloud's API for `/.well-known` URIs handle all other
+            # requests by passing them to the front-end controller.
+            return 301 /index.php$request_uri;
+        }
         # Rules borrowed from `.htaccess` to hide certain paths from clients
         location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)(?:$|/)  { return 404; }
@@ Zeile 114: / Zeile 173: @@
             fastcgi_param front_controller_active true;     # Enable pretty urls
             #fastcgi_pass php-handler;
-	    fastcgi_pass unix:/run/php/php7.3-fpm.sock;
+	    fastcgi_pass unix:/run/php/php8.2-fpm.sock;
             fastcgi_intercept_errors on;
@@ Zeile 138: / Zeile 197: @@
 }
 </file>
-  - PHP-Konfiguration für Upload anpassen<file|/etc/php/7.3/fpm/pool.d/www.conf>
+  - PHP-Konfiguration für Upload anpassen<file|/etc/php/8.2/fpm/pool.d/www.conf>
 ...
 clear_env = no
@@ Zeile 149: / Zeile 208: @@
 ...
 </file>
-  - PHP-Konfiguration für Upload anpassen<file|/etc/php/7.3/fpm/php.ini>
+  - PHP-Konfiguration für Upload anpassen<file|/etc/php/8.2/fpm/conf.d/99-local.ini>
-...
-; Output buffering is a mechanism for controlling how much output data
-; (excluding headers and cookies) PHP should keep internally before pushing that
-; data to the client. If your application's output exceeds this setting, PHP
-; will send that data in chunks of roughly the size you specify.
-; Turning on this setting and managing its maximum buffer size can yield some
-; interesting side-effects depending on your application and web server.
-; You may be able to send headers and cookies after you've already sent output
-; through print or echo. You also may see performance benefits if your server is
-; emitting less packets due to buffered output versus PHP streaming the output
-; as it gets it. On production servers, 4096 bytes is a good setting for performance
-; reasons.
 output_buffering = 0
-...
-; Maximum execution time of each script, in seconds
-; http://php.net/max-execution-time
-; Note: This directive is hardcoded to 0 for the CLI SAPI
 max_execution_time = 1800
-...
-; Maximum amount of time each script may spend parsing request data. It's a good
-; idea to limit this time on productions servers in order to eliminate unexpectedly
-; long running scripts.
 max_input_time = 1800
-...
-; Maximum amount of memory a script may consume (128MB)
-; http://php.net/memory-limit
 memory_limit = 512M
-...
-; Temporary directory for HTTP uploaded files (will use system default if not
-; specified).
-; http://php.net/upload-tmp-dir
 upload_tmp_dir = /var/www/tmp
-...
-; Maximum size of POST data that PHP will accept.
-; Its value may be 0 to disable the limit. It is ignored if POST data reading
-; is disabled through enable_post_data_reading.
-; http://php.net/post-max-size
 post_max_size = 512M
-...
-; Maximum allowed size for uploaded files.
-; http://php.net/upload-max-filesize
 upload_max_filesize = 512M
-...
+opcache.interned_strings_buffer = 128
 </file>
   - Dienste aktivieren und neustarten
-    * **sudo systemctl enable nginx.service php7.3-fpm.service**
+    * **sudo systemctl enable nginx.service php8.2-fpm.service**
-    * **sudo systemctl restart nginx.service php7.3-fpm.service**
+    * **sudo systemctl restart nginx.service php8.2-fpm.service**
 ==== Nextcloud ====
@@ Zeile 202: / Zeile 226: @@
   - Nextcloud-Verzeichnisse erstellen
     * **sudo mkdir /var/www/{public_html,data,tmp}**
+  - Cronjob einrichten
+    * **sudo crontab -u www-data -e**<code>
+*/5 * * * * php -f /var/www/public_html/cron.php
+</code>
 Es wurde eine bereits bestehende Installation übernommen.
@@ Zeile 218: / Zeile 246: @@
         - /root
         - /var/log
-        - /var/www
+        - /var/www/data
+        - /var/www/public_html
 ...
 </file>