cphipps/watchstate
1
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

Fix minor typo

Browse Source
This commit is contained in:
arabcoders
2025-04-06 22:27:34 +03:00
parent a2ad6170b5
commit d0ea7c7678
3 changed files with 10 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
FAQ.md
View File

@@ -259,9 +259,10 @@ map:
#.... more users
```
If you create a map for a user, it SHOULD include all the backends you want to sync the user data with. while th matcher
might automatically detect the other backends even if not included in the map, it best to manually set them in group to
prevent any issues that might arise. Each list item is a user, and each user has a list of backends. Each backend
If you create a map for a user, it SHOULD include all the backends you want to sync the user data with. while the
matcher might automatically detect the other backends even if not included in the map, it best to manually set them in
group to prevent any issues that might arise. Each list item is a user, and each user has a list of backends. Each
backend.
> [!NOTE]
> the backend names `my_plex_server`, `my_jellyfin_server`, `my_emby_server` are the names you have chosen for

2
README.md
View File

@@ -14,7 +14,7 @@ out of the box, this tool support `Jellyfin`, `Plex` and `Emby` media servers.
We have recently re-worked how the `backend:create` command works, and we no longer generate random name for invalid
backends names or usernames. We do a normalization step to make sure the name is valid. This should help with the
confusion of having random names. This means if you re-run the `backend:create` you most likely will get a different
name then before. So, we suggest to re-run the command with `--re-create` flag. This flag will delete the current
name than before. So, we suggest to re-run the command with `--re-create` flag. This flag will delete the current
sub-users, and regenerate updated config files.
We have also added new guard for the command, so if you already generated your sub-users, re-running the command will

11
src/Commands/Backend/CreateUsersCommand.php
View File

@@ -579,19 +579,18 @@ class CreateUsersCommand extends Command
<<<Text
<error>ERROR:</error> Users configuration already exists.
If you want to re-create the users configuration, run the same command with [<flag>-r, --re-create</flag>] flag,
This will do the following:
If you want to re-create the users configuration, run the same command with [<flag>-r, --re-create</flag>] flag, This will do the following:
1. Delete the current sub-users configuration and data.
2. Re-create the sub-users configuration.
Otherwise, you can use the [<flag>--run</flag>] to keep current configuration and update it with the new
users.
Otherwise, you can use the [<flag>--run</flag>] to keep current configuration and update it with the new users.
<value>
Beware, we have recently changed how we do matching, most likely if you run without re-creating the configuration.
it will result in double users for same user or more.
</value>
<notice>
-------
We suggest to re-create the configuration. If you generated your users before date 2025-04-06.
</notice>
Text