From a2e98a166be84fcefb10fc879b1e7e80c672386e Mon Sep 17 00:00:00 2001 From: "Abdulmhsen B. A. A" Date: Fri, 15 Sep 2023 16:39:14 +0300 Subject: [PATCH] Updated README & FAQ. also updated auto builder to include date into our version numbers. --- .github/workflows/build.yml | 4 ++-- FAQ.md | 6 ++++++ README.md | 17 ----------------- 3 files changed, 8 insertions(+), 19 deletions(-) diff --git a/.github/workflows/build.yml b/.github/workflows/build.yml index ffcc6678..5e415c50 100644 --- a/.github/workflows/build.yml +++ b/.github/workflows/build.yml @@ -88,9 +88,9 @@ jobs: ${{ env.GHCR_SLUG }} tags: | type=raw,value=latest,enable=${{ endsWith(github.ref, github.event.repository.default_branch) }} - type=ref,event=tag type=ref,event=branch - type=sha,enable=${{ endsWith(github.ref, github.event.repository.default_branch) }} + type=ref,event=tag + type=raw,value=${{branch}}-{{date 'YYYYMMDD'}}-{{sha}} flavor: | latest=false diff --git a/FAQ.md b/FAQ.md index 3cdd73e6..18e04395 100644 --- a/FAQ.md +++ b/FAQ.md @@ -509,4 +509,10 @@ something like `redis://redis:6379?password=my_secert_password&db=8`. We only su Once that done, restart the container. +### There are weirdly named directories in my data path? +Unfortunately, That was due to a bug introduced in (2023-09-12 877a41a) and was fixed in (2023-09-19 a2f8c8a), if you +have happened to installation or update during this period, you will have those directories. To fix this issue, you +can simply delete those folders `%(tmpDir)` `%(path)` `{path}` `{tmpDir}`. I decided to not do it automatically to avoid +any data loss. you should check the directories to make sure they are empty. if not copy the directories to the correct +location and delete the empty directories. diff --git a/README.md b/README.md index e6b4f15b..893f5c3d 100644 --- a/README.md +++ b/README.md @@ -14,23 +14,6 @@ out of the box, this tool support `Jellyfin`, `Plex` and `Emby` media servers. ---- -### Breaking change in plex webhook handling. - -If you happen to have enabled plex webhooks and had `limit webhook requests to the selected user`, plex in recent -versions managed to fix bug in old versions where they report the admin account user id as `1` regardless of whether you -have single or multi-user setup. We have a fix in place `(2023-08-28)` to update the user id to the actual user id from -plex.tv. However, Sadly this step is manual you have to rerun the `config:manage` command and re-select your user to -update the value. To fix this please run the command - -```bash -$ docker exec -ti watchstate config:manage [BACKEND_NAME] -``` - -And select your actual user which you want to process the webhooks events from. once that fixed you won't be missing -events from webhooks. - ----- - # Install create your `docker-compose.yaml` with the following content: