grtgbln

> attempt to write a readonly database Sounds like a permissions issue between the container and the database file you created.

RE: Port, update to template coming in the next few hours: RE: iGPU, as far as I know, LocalAI only supports Nvidia CUDA, not iGPU. https://localai.io/features/gpu-acceleration/index.html

You should just need to restart the app now that the file it expects is there.

Run touch anythingllm.db from inside your "/mnt/user/appdata/anythingllm" folder. I have just updated the template to mention this.

I just pushed out an update to the template that should fix this, check back tomorrow once it's synced.

You'll need some kind of integration that can use the models. I'd recommend a GUI like bigAGI: https://localai.io/docs/integrations/

Thanks for letting me know. The `.env` file must exist before running, otherwise Docker will try to make it (and assumes it's a folder, not a file). I have updated the template to note that.

Is there a way to mitigate breaking changes and/or major versions in a CA template? One app I manage a template for has a new major (x.y.z) version out, which requires changes to both the Docker/CA settings (some new config fields, some removed, some changed type from a string to a dropdown option) and to non-Docker settings (permission changes to the remote API the app interacts with via the provider's portal). 1. Is there a process that I can take to properly migrate user settings from the old "string" type to the new "dropdown" type? If not, is there a way to call this out to the user or force them to view the app's configuration page during an update? 2. In the same vain, is there a way to stop users from auto-updating to a new major version, or bring attention to it? It doesn't seem like there's necessarily versioning for CA templates. The container currently uses `Branch` for which Docker image to use, but with `latest` being the only option. Perhaps changing the only available branch to a specific older image?

As the error suggests, your command is incorrect. You need to provide the "-c" flag when providing a config file path. Use the following instead: python run.py -c /mnt/user/appdata/prerolls/config.yaml Also, please reserve this thread for discussion specifically about running this Community App as a Docker container on Unraid. For general questions about running the Python script directly, please open an issue on the project's GitHub page: https://github.com/nwithan8/plex-prerolls

Thank you for bringing the bug to my attention, it has been patched and will be available in the latest version shortly. The masking of the cron template has also been fixed. In the future, please open an issue on GitHub about the project: https://github.com/nwithan8/plex-prerolls, I check that more often than I check these forums.

The path "/mnt/user/data/media/..." doesn't exist inside Plex. You need to use the path to each file as Plex would see it, perhaps something like "/media/...". Refer to the mapped paths on your Plex Docker container. Also, those Fall, Winter et. al schedules won't work with just paths to the prerolls folders, you need to include full paths to individual media files (not sure if perhaps you redacted those for this help session)

The Docker container does not need to access the pre-roll files directly. In your schedule, use the path that Plex would use to access each file.

A second application release: Plex Prerolls GitHub: https://github.com/nwithan8/plex-prerolls Docker: https://hub.docker.com/repository/docker/nwithan8/plex_prerolls/general This application parses a simple schedule and, on a cron job, updates the prerolls used by Plex before a movie.

Apologies, I haven't been on the forums in a while. Did this resolve itself?

Yes, Squid has mentioned that to me. I didn't do a search for ntfy before making the template. I mostly was seeking to get Tauticord released.