Различия

Показаны различия между двумя версиями страницы.

--- dokumenty:obnovlenie_servisov [2025/09/27 06:33] – dikobraz
+++ dokumenty:obnovlenie_servisov [2025/09/27 07:00] (текущий) – dikobraz
@@ Строка 2: / Строка 2: @@
 ===== Install =====
-  * Элемент ненумерованного списка
   * Download and extract the installer package
   * Execute traccar.run file
-    * sudo ./traccar.run
+    * <code bash>sudo ./traccar.run</code>
   * Start systemd service
-    * sudo systemctl start traccar
+    * <code bash>sudo systemctl start traccar</code>
 ===== Uninstall =====
@@ Строка 15: / Строка 14: @@
     * sudo systemctl stop traccar
   * Remove systemd service
-    * sudo systemctl disable traccar
+    * <code bash>
-    * sudo rm /etc/systemd/system/traccar.service
+sudo systemctl disable traccar
-    * sudo systemctl daemon-reload
+sudo rm /etc/systemd/system/traccar.service
+sudo systemctl daemon-reload</code>
   * Remove traccar directory
-    * sudo rm -R /opt/traccar
+    * <code bash>sudo rm -R /opt/traccar</code>
+===== Run as Non-Root User =====
+Running services as root is not a good practice. In favour of Traccar being deployable as easy as possible, we made the compromise of not tieing Traccar to running as a specific user.
+That being said, we highly recommend you do not run Traccar as root user.
+You can achive this by adding a systemd Drop-In to the traccar.service. For that, follow these steps:
+<code bash>
+mkdir /etc/systemd/system/traccar.service.d/
+touch /etc/systemd/system/traccar.service.d/run-as-user.conf</code>
+The content of the file should set the user for traccar to the one you want to run it as. Keep in mind, that the Traccar directory has, of course, to be readable and writable by that user.
+<code>
+[Service]
+User=traccar
+Group=traccar</code>
 ===== Upgrading Traccar =====
@@ Строка 34: / Строка 50: @@
   - Restore the **traccar.xml** configuration file (if applicable).
   - Start the Traccar service.
+====== Nextcloud ======
+====== Firefly iii ======
+===== Upgrade a self-managed server =====
+Firefly III can upgrade itself from very old versions, even back from 4.7.x. In some cases the upgrade process is destructive. It will remove transactions, delete accounts or clean up data.
+Warning
+Always make a backup of your database and storage before you upgrade, especially when you upgrade major versions.
+Created using composer "create-project"
+The best way to upgrade is to use the "Straight from GitHub" instructions below. In recent times, the deployment of Firefly III has changed and the "create-project" method is no longer recommended.
+Straight from GitHub
+==== Upgrading by pulling the remote repository ====
+It's no longer possible to upgrade Firefly III by pulling the code from the main or develop branch of the repository. Generated (JS) code and other dependencies are not in the repository, so your upgraded installation may not work as expected.
+v6.4.0 is the latest version.
+    Download the latest release as a zip file from GitHub.
+    Download the latest release as a tar.gz file from GitHub.
+It is up to you, if you prefer the tar.gz file or the zip file.
+Validate the downloaded archive
+Optionally, you can validate and test the integrity of your download by also downloading the SHA256 checksum file.
+    SHA256 checksum file of the zip file.
+    SHA256 checksum file of the tar.gz file.
+With this SHA256 checksum file, you can verify the integrity of the download by running the following command:
+<code bash>
+# Should return: "FireflyIII-v6.4.0.zip: OK"
+sha256sum -c FireflyIII-v6.4.0.zip.sha256
+sha256sum -c FireflyIII-v6.4.0.tar.gz.sha256
+# alternative command:
+shasum -a 256 -c FireflyIII-v6.4.0.zip.sha256
+shasum -a 256 -c FireflyIII-v6.4.0.tar.gz.sha256
+</code>
+==== Move the old installation ====
+Move the old installation to a temporary directory, ie firefly-iii-old. Example commands:
+<code bash>
+# moves the entire installation to a backup directory.
+# this also serves as an impromptu backup of your installation
+mv /var/www/firefly-iii /var/www/firefly-iii-old
+</code>
+==== Extract the archive ====
+Extract the archive with the new release wherever you had installed Firefly III. In this example, it is /var/www/firefly-iii, but it could be anywhere. To do this over the command line, use the following command:
+<code bash>
+# The destination directory can be changed, of course.
+mkdir /var/www/firefly-iii
+unzip -o FireflyIII-v6.4.0.zip -x "storage/*" -d /var/www/firefly-iii
+# a tar.gz alternative:
+mkdir /var/www/firefly-iii
+tar -xvf FireflyIII-v6.4.0.tar.gz -C /var/www/firefly-iii --exclude='storage'
+</code>
+Use sudo if necessary, but if you do, make sure that you set the ownership of the /var/www/firefly-iii directory to www-data again:
+<code bash>
+# The destination directory can be changed, of course.
+sudo chown -R www-data:www-data /var/www/firefly-iii
+sudo chmod -R 775 /var/www/firefly-iii/storage
+</code>
+==== Exclude the storage directory ====
+When unpacking, make sure you do not overwrite the storage directory. That's why the -x "storage/*" and --exclude='storage' part is important. It prevents the default storage directory from being extracted. You will overwrite it anyway from the old installation directory.
+Copy over files from the old version
+Copy the .env file and the entire storage folder from the old installation to the new one. Example commands:
+<code bash>
+# copy the .env file
+cp /var/www/firefly-iii-old/.env /var/www/firefly-iii/.env
+# copy the storage directory
+cp -r /var/www/firefly-iii-old/storage /var/www/firefly-iii
+</code>
+==== Run upgrade commands ====
+Run the following commands to upgrade the database and the application:
+<code bash>
+php artisan migrate --seed
+php artisan cache:clear
+php artisan view:clear
+php artisan firefly-iii:upgrade-database
+php artisan firefly-iii:laravel-passport-keys
+</code>