Blame
|
1 | # Upgrade Guide |
||||||
| 2 | ||||||||
| 3 | Comprehensive upgrade guide for Docker and Standalone Windows/Linux Executables. |
|||||||
| 4 | ||||||||
| 5 | Regardless of how your LubeLogger instance is installed/configured, we highly recommend that you create a backup before updating, it will take less than two minutes of your time and save you a lot of headache if something goes wrong. |
|||||||
| 6 | ||||||||
| 7 | ## Create A Backup |
|||||||
| 8 | ||||||||
| 9 | ### Manual Method |
|||||||
| 10 | ||||||||
| 11 | Login as the root/superuser to your LubeLogger instance, navigate to the Settings tab and create a backup |
|||||||
| 12 | ||||||||
| 13 |  |
|||||||
| 14 | ||||||||
| 15 | A zip file will be downloaded to your computer. |
|||||||
| 16 | ||||||||
| 17 | ### Automated Method |
|||||||
| 18 | ||||||||
| 19 | Use a script to hit the API endpoint for creating backups, see [[API|Advanced/API#example-use-cases]] |
|||||||
| 20 | ||||||||
| 21 | You can automate the script using a cron job to create daily or weekly backups. |
|||||||
| 22 | ||||||||
| 23 | ## Docker |
|||||||
| 24 | ||||||||
| 25 | 1. Create a backup |
|||||||
| 26 | 2. Verify your Docker Volumes |
|||||||
| 27 | 3. Run the command `docker compose pull` |
|||||||
| 28 | 4. The, run the command `docker compose up` to start the container |
|||||||
| 29 | ||||||||
| 30 | If your Docker Volumes are bound and persisted correctly, you should have no loss of data. |
|||||||
| 31 | ||||||||
| 32 | ## Windows/Linux Standalone |
|||||||
| 33 | ||||||||
| 34 | 1. Create a backup |
|||||||
|
35 | 2. Download the latest version of LubeLogger from the Release section |
||||||
| 36 | 3. Extract the archive over your existing LubeLogger installation. |
|||||||
| 37 | 4. Restore the backup if there is data loss |
|||||||
