aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorIvan Tashkinov <ivantashkinov@gmail.com>2019-11-18 20:43:19 +0300
committerIvan Tashkinov <ivantashkinov@gmail.com>2019-11-18 20:43:19 +0300
commit3aaf3aa2c24c6b38d7e49e4861c1294c285db49b (patch)
tree7457b8b922a3ebe1595566a55cde1d846cdde05d /docs
parentaad6576130c3e47a5fcc102c736ce6414c0efd7a (diff)
parent06151776c0c2c529a1bd3b4866162794c141e95f (diff)
downloadpleroma-3aaf3aa2c24c6b38d7e49e4861c1294c285db49b.tar.gz
Merge remote-tracking branch 'remotes/upstream/develop' into 1335-user-api-id-fields-relations
Diffstat (limited to 'docs')
-rw-r--r--docs/API/admin_api.md8
-rw-r--r--docs/administration/CLI_tasks/database.md3
2 files changed, 3 insertions, 8 deletions
diff --git a/docs/API/admin_api.md b/docs/API/admin_api.md
index 9d914c9a6..f64983a90 100644
--- a/docs/API/admin_api.md
+++ b/docs/API/admin_api.md
@@ -235,14 +235,6 @@ Note: Available `:permission_group` is currently moderator and admin. 404 is ret
}
```
-## DEPRECATED `PATCH /api/pleroma/admin/users/:nickname/activation_status`
-
-### Active or deactivate a user
-
-- Params:
- - `nickname`
- - `status` BOOLEAN field, false value means deactivation.
-
## `GET /api/pleroma/admin/users/:nickname_or_id`
### Retrive the details of a user
diff --git a/docs/administration/CLI_tasks/database.md b/docs/administration/CLI_tasks/database.md
index 484639231..3011646c8 100644
--- a/docs/administration/CLI_tasks/database.md
+++ b/docs/administration/CLI_tasks/database.md
@@ -2,6 +2,9 @@
Every command should be ran with a prefix, in case of OTP releases it is `./bin/pleroma_ctl database` and in case of source installs it's `mix pleroma.database`.
+!!! danger
+ These mix tasks can take a long time to complete. Many of them were written to address specific database issues that happened because of bugs in migrations or other specific scenarios. Do not run these tasks "just in case" if everything is fine your instance.
+
## Replace embedded objects with their references
Replaces embedded objects with references to them in the `objects` table. Only needs to be ran once if the instance was created before Pleroma 1.0.5. The reason why this is not a migration is because it could significantly increase the database size after being ran, however after this `VACUUM FULL` will be able to reclaim about 20% (really depends on what is in the database, your mileage may vary) of the db size before the migration.