Diverts to `install.php` after pulling latest image about images

[LeoColomb]

Thanks for filing this issue, @Svampebob1.
Indeed, per default, a container data is not persistent and therefore lost when recreated. This is true for YOURLS configuration.
To keep the configuration, a volume must be created to store the config data into a persistent storage.
In our case, a volume on /var/www/html/user/config.php. In fact, it might be useful/simpler to mount the whole user folder, /var/www/html/user.

The update is blocked when the entire YOURLS location is mounted, /var/www/html, to avoid file mismatch.

I'm closing the issue as answered, but don't hesitate to continue the discussion below is needed.

[Svampebob1]

I'm sorry, but I've lost all my short URLs again. I see that there has been an update two days ago.
I'm using watchtower for automatic updates. I've disabled this for this image, until I've found a solution.

What is the best practice on upgrading this image, without data?
I'm thinking about taking regular backups, so that I can restore when this happens the next time.
In case of backup and restore, where are the short URLs stored?

[LeoColomb]

What is the best practice on upgrading this image, without data?

First you must elaborate on which data you are talking about:

• As of your original report, you were talking about configuration data. The way to handle the configuration has been described in my previous answer.
• Now you are mentionning the lost of application data, i.e. actual links, which are stored on a external database. By external, it mease this database is independant of YOURLS, thus not affected by YOURLS updates.
  Please refer to this database documentation on how to handle it properly. If you are using MySQL, see its container usage documentation here: https://hub.docker.com/_/mysql

[Svampebob1]

Sorry. It was supposed to be "without loosing data". To be more specific: Without loosing my short URLs.

I've been using the example for docker compose from Docker hub. But I understand the problem now. I've been assuming that the short URLs has been stored as a file and logons has been stored in the database. But I see now that this is a completely wrong assumption.

Thanks for your help 👍️.

[Svampebob1]

To anyone else having the same issue, you can use the following Docker compose template for setting up Yourls:

version: '3.1'

services:

  yourls:
	image: yourls
	restart: always
	volumes:
	  - /--path-to-yourls--/yourls/user:/var/www/html/user   
	ports:
	  - 8083:80
	environment:
	  YOURLS_DB_PASS: --root DB password--
	  YOURLS_SITE: https://--url for yourls--
	  YOURLS_USER: --login user--
	  YOURLS_PASS: --login password--
	depends_on:
	  - mysql

  mysql:
	image: mysql
	restart: always
	environment:
	  MYSQL_ROOT_PASSWORD: --root DB password--
	  MYSQL_DATABASE: yourls
	volumes:
	  - /--path to yourls--/yourls/mysql-data:/var/lib/mysql