From af163d9c50a4e185b1bd67791e9f5c6141fbf5fb Mon Sep 17 00:00:00 2001
From: Simon <simobilleter@gmail.com>
Date: Sat, 2 Sep 2023 12:17:48 +0700
Subject: [PATCH] add more reactivate commands

---
 mkdocs/docs/advanced.md | 52 ++++++++++++++++++++++++++++++++++++-----
 1 file changed, 46 insertions(+), 6 deletions(-)

diff --git a/mkdocs/docs/advanced.md b/mkdocs/docs/advanced.md
index 5c14afe..cfc2348 100644
--- a/mkdocs/docs/advanced.md
+++ b/mkdocs/docs/advanced.md
@@ -9,19 +9,21 @@ description: Collection of advanced concepts and debug info.
 
 A loose collection of advanced debug info, may or may not apply to you, only use this when you know what you are doing. Some of that functionality might get implemented in the future in the regular UI.
 
-## Reactivate all Videos
-As part of the metadata refresh task, Tube Archivist will mark videos as deactivated, if they are no longer available on YouTube. For some reasons, that might have deactivated videos that shouldn't have, for example if a video got reinstated after a copyright strike on YT. You can reactivate all videos in bulk, so the refresh task will check them again and deactivate the ones that are actually not available anymore.
+## Reactivate documents
+As part of the metadata refresh task, Tube Archivist will mark videos, channels and playlists as deactivated, if they are no longer available on YouTube. For some reasons, that might have deactivated something that shouldn't have, for example if a video got reinstated after a copyright strike on YT. You can reactivate all things in bulk, so the refresh task will check them again and deactivate the ones that are actually not available anymore.
 
-Run this curl command from within the TA container:
+Curl commands to run within the TA container.
+
+Reactivate all videos:
 
 ```bash
 curl -XPOST "$ES_URL/ta_video/_update_by_query?pretty" -u elastic:$ELASTIC_PASSWORD -H "Content-Type: application/json" -d '
 {
   "query": {
 	"term": {
-  	"active": {
-    	"value": false
-  	}
+		"active": {
+			"value": false
+		}
 	}
   },
   "script": {
@@ -31,6 +33,44 @@ curl -XPOST "$ES_URL/ta_video/_update_by_query?pretty" -u elastic:$ELASTIC_PASSW
 }'
 ```
 
+Reactivate all channels:
+
+```bash
+curl -XPOST "$ES_URL/ta_channel/_update_by_query?pretty" -u elastic:$ELASTIC_PASSWORD -H "Content-Type: application/json" -d '
+{
+  "query": {
+	"term": {
+		"channel_active": {
+			"value": false
+		}
+	}
+  },
+  "script": {
+	"source": "ctx._source.channel_active = true",
+	"lang": "painless"
+  }
+}'
+```
+
+Reactivate all playlists:
+
+```bash
+curl -XPOST "$ES_URL/ta_video/_update_by_query?pretty" -u elastic:$ELASTIC_PASSWORD -H "Content-Type: application/json" -d '
+{
+  "query": {
+	"term": {
+		"playlist_active": {
+			"value": false
+		}
+	}
+  },
+  "script": {
+	"source": "ctx._source.playlist_active = true",
+	"lang": "painless"
+  }
+}'
+```
+
 ## Corrupted ES index reset
 After a hard reset of your server or any other hardware failure you might experience data corruption. ES can be particularly unhappy about that, especially if the reset happens during actively writing to disk. It's very likely that only your `/indices` folder got corrupted, as that is where the regular read/writes happen. Luckily you have your [snapshots](settings.md#snapshots) set up.