Различия
Показаны различия между двумя версиями страницы.
| Предыдущая версия справа и слева Предыдущая версия Следующая версия | Предыдущая версия | ||
| dokumenty:obnovlenie_servisov [2025/09/27 06:44] – dikobraz | dokumenty:obnovlenie_servisov [2025/09/27 07:00] (текущий) – dikobraz | ||
|---|---|---|---|
| Строка 3: | Строка 3: | ||
| ===== Install ===== | ===== Install ===== | ||
| - | * Элемент ненумерованного списка | ||
| * Download and extract the installer package | * Download and extract the installer package | ||
| * Execute traccar.run file | * Execute traccar.run file | ||
| - | * < | + | * < |
| * Start systemd service | * Start systemd service | ||
| - | * < | + | * < |
| ===== Uninstall ===== | ===== Uninstall ===== | ||
| Строка 15: | Строка 14: | ||
| * sudo systemctl stop traccar | * sudo systemctl stop traccar | ||
| * Remove systemd service | * Remove systemd service | ||
| - | * < | + | * < |
| sudo systemctl disable traccar | sudo systemctl disable traccar | ||
| sudo rm / | sudo rm / | ||
| sudo systemctl daemon-reload</ | sudo systemctl daemon-reload</ | ||
| * Remove traccar directory | * Remove traccar directory | ||
| - | * < | + | * < |
| ===== Run as Non-Root User ===== | ===== Run as Non-Root User ===== | ||
| Строка 29: | Строка 28: | ||
| You can achive this by adding a systemd Drop-In to the traccar.service. For that, follow these steps: | You can achive this by adding a systemd Drop-In to the traccar.service. For that, follow these steps: | ||
| - | < | + | < |
| mkdir / | mkdir / | ||
| touch / | touch / | ||
| Строка 53: | Строка 52: | ||
| ====== Nextcloud ====== | ====== 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, | ||
| + | |||
| + | Warning | ||
| + | |||
| + | Always make a backup of your database and storage before you upgrade, especially when you upgrade major versions. | ||
| + | Created using composer " | ||
| + | |||
| + | The best way to upgrade is to use the " | ||
| + | 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: " | ||
| + | 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 | ||
| + | </ | ||
| + | ==== 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 / | ||
| + | </ | ||
| + | |||
| + | ==== Extract the archive ==== | ||
| + | |||
| + | Extract the archive with the new release wherever you had installed Firefly III. In this example, it is / | ||
| + | <code bash> | ||
| + | # The destination directory can be changed, of course. | ||
| + | mkdir / | ||
| + | unzip -o FireflyIII-v6.4.0.zip -x " | ||
| + | |||
| + | # a tar.gz alternative: | ||
| + | mkdir / | ||
| + | tar -xvf FireflyIII-v6.4.0.tar.gz -C / | ||
| + | </ | ||
| + | Use sudo if necessary, but if you do, make sure that you set the ownership of the / | ||
| + | <code bash> | ||
| + | # The destination directory can be changed, of course. | ||
| + | sudo chown -R www-data: | ||
| + | sudo chmod -R 775 / | ||
| + | </ | ||
| + | |||
| + | ==== Exclude the storage directory ==== | ||
| + | |||
| + | When unpacking, make sure you do not overwrite the storage directory. That's why the -x " | ||
| + | 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 / | ||
| + | |||
| + | # copy the storage directory | ||
| + | cp -r / | ||
| + | </ | ||
| + | |||
| + | ==== 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: | ||
| + | php artisan firefly-iii: | ||
| + | </ | ||