General upgrade guide
Please follow these instructions to upgrade LinkAce to a newer version.
Upgrade a Docker installation
LinkAce has its own update script which will guide you trough the update process. You can download the script from the repository: update-docker.sh
Alternatively, you can run all actions on your own. This might be helpful if you have a non-standard environment.
- Stop your current containers:
docker-compose down - This step only applies to the advanced setup method. Delete the current app volume, where
linkace_linkace_appis the name of your volume. You may find the exact name by runningdocker volume ls, the volume must end withlinkace_app.docker volume rm linkace_linkace_app - Pull the new image:
docker pull linkace/linkace - Restart your container:
docker-compose up -d - Run the database migrations and delete the current cache:
You may get a warning about running the migration in production mode. You should confirm the migration by answering withdocker exec -it linkace_app_1 php artisan migrate docker exec -it linkace_app_1 php artisan cache:clear docker exec -it linkace_app_1 php artisan settings:clear-cacheyes.
Make sure to check the version-specific upgrade guides to make sure you don’t miss additional important steps.
Upgrade a non-Docker installation
- Get the latest version of LinkAce by downloading the package from the releases page.
Overwrite all existing files with the new ones. If you want to keep your log files, skip the
storage/logsfolder. - Run the database migrations which are needed after all updates and delete the current cache:
You may get a warning about running the migration in production mode. You should confirm the migration by answering withphp artisan migrate php artisan cache:clear php artisan settings:clear-cacheyes. Make sure to check the version-specific upgrade guides to make sure you don’t miss additional important steps.
Version-specific upgrades
to version 2.5.4
LinkAce now requires you to add
APP_URL=https://my-linkace-domain.com to your .env file or alternatively to your docker compose file. Replace https://my-linkace-domain.com with the actual URL of your LinkAce instance.
This is needed to mitigate a possible security issue if you don’t have trusted proxies configured, which is the default for LinkAce. Not adding this setting will break some features such as password reset emails.