Advanced config changes don't persist #14
Replies: 10 comments
|
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:
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: This might change with future releases. |
|
Is database.sqlite required when using a mysql db? |
In that case, it is not required. |
|
Last question (i think lol), what is |
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) |
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). We still even have the original comments from LittleLink in the source code, so this project was kept very close to the source material. |

Uh oh!
There was an error while loading. Please reload this page.
Using the latest version of LLC, I've noticed a few times now that changes I make to the Advanced config don't get saved between container restarts. Is there some file I need to mount so it persists?
All reactions