I'm currently working on including data persistence in the documentation.

The easiest solution I came up with is moving the entire web application to a persistent volume.

Something like this:

1. Create volume:
   docker volume create llc

2. Running the Docker image normally while mounting the volume:
   docker run --detach --name littlelink-custom --publish 80:80 --publish 443:443 --restart unless-stopped --mount source=llc,target=/htdocs julianprieber/littlelink-custom

--mount source=llc,target=/htdocs julianprieber/littlelink-custom

Let me know how this worked for you, and I'll include it in the docs 👍

I don't know about the inner workings of this specific app, but I usually like to keep mounted things for only specific config (rather than entire apps where some or many of the files never change). There's already a database in use for LLC; is it possible to just save the changes (and use them) from a db table in it?

If you wish to save only selective files, you should save the following files and folders:

/htdocs/.env
/htdocs/database/database.sqlite
/htdocs/config/advanced-config.php
/htdocs/littlelink/images/avatar.png
/htdocs/themes (folder)
/htdocs/img (folder)

This might change with future releases.

Is database.sqlite required when using a mysql db?

Is database.sqlite required when using a mysql db?

In that case, it is not required.

Last question (i think lol), what is /htdocs/littlelink/images/avatar.png for (like, where is it used) ? I'm confused because the user uploads their avatar in their profile and it gets saved in img, and also because it's an actual .png instead of an editable file, unless it is often deleted and re-saved as the same file name by LLC?

The avatar.png is used to store the custom site logo.

chrome_xFp7lY1FID

If you do not plan on using that one, you can skip that as well.

The avatar.png is used to store the custom site logo.

chrome_xFp7lY1FID

If you do not plan on using that one, you can skip that as well.

ok thanks :)

just so I fully understand, if I change the logo, it deletes this one and renames the uploaded one to "avatar.png?" (and how come the logo is called an avatar? haha)

just so I fully understand, if I change the logo, it deletes this one and renames the uploaded one to "avatar.png?" (and how come the logo is called an avatar? haha)

Yup, pretty much like that.

I can't really say for certain why the image is called that by I think I got a fairly good understanding why.

This function was implemented in the application LLC is forked from (https://github.com/khzg/littlelink-admin).
This thing is again based on the plain HTML project LittleLink (https://github.com/sethcottle/littlelink). In this thing, the profile image on the "home page" is called avatar.png in the files. So I think Khashayar just kept that name when implementing this.

We still even have the original comments from LittleLink in the source code, so this project was kept very close to the source material.

0c72b57