Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Templates don't persist when removing the docker container #161

Open
ioqy opened this issue Jun 29, 2024 · 3 comments
Open

Templates don't persist when removing the docker container #161

ioqy opened this issue Jun 29, 2024 · 3 comments

Comments

@ioqy
Copy link

ioqy commented Jun 29, 2024

Version running
latest docker build

Describe the bug
The templates are either gone after recreating the continer (e.g. with docker compose down and docker compose up) or the default templates default and audio only are added even though they have been deleted.

After a bit of searching I found that the templates are stored in the /config directory. So I added it as a volume to the docker compose file but the local.db gets either completely overwritten after the container is recreated or the default templates are added again.

Additional context
It would be nice to already have the /config directory in the docker compose example instead of having to "reverse engineer" where things are stored.

@marcopeocchi
Copy link
Owner

hello @ioqy,

If the dockerfile entrypoint is not overwritten and the /config volume set, the local.db will not be recreated.
As for the default templates: they're re-added since if the container is recreated or restarted the application lose its "state".

The docker-compose.yml example has been updated in 98f0ea3.

@ioqy
Copy link
Author

ioqy commented Jul 2, 2024

As for the default templates: they're re-added since if the container is recreated or restarted the application lose its "state".

I would have expected that the database is for keeping the "state".

The docker-compose.yml example has been updated in 98f0ea3.

That's great!

marcopeocchi added a commit that referenced this issue Jul 8, 2024
@marcopeocchi
Copy link
Owner

I would have expected that the database is for keeping the "state".

I know it's silly. Design flaw.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants