Added need_reboot endpoint to admin api

Closes #1677

See merge request !2373

Improve documentation of mrf_object_age

See merge request pleroma/pleroma!2305

Admin API: `PATCH /api/pleroma/admin/users/:nickname/update_credentials`

See merge request !2149

Every time someone tries to use it, it goes mad and tries to scrape the
entire fediverse for no visible reason, it's better to just remove it
than continue shipping it in it's current state.

idea acked by lain and feld on irc

Closes #1595 #1422

Related: #1594

CLI_tasks/user.md: Fix `pleroma.user new` documentation

Closes #1621

See merge request !2286

Needs to be backported to stable.

Related: pleroma/pleroma-support#29

A warning was added, but their were some newlines and whitespaces missing which broke the rendering of the setting. I've added them now

Add warning to the fetch_initial_posts setting. Now we sometimes have people who enable this without realising the consequences (tons of posts being fetcht as each fetch makes Pleroma discover new users)
I also made a more explicit distinction between OTP and from source installs in the general explanation

Admin API: Exclude boosts from `GET /api/pleroma/admin/users/:nickname/statuses` and `GET /api/pleroma/admin/instance/:instance/statuses`

Ilja authored 5 years ago and lain committed 5 years ago

I added a new file to explain
* where a custom theme can be created
* where themes can be downloaded
* where to add the theme on the server
* how to make the theme available on the instance
* how to set the theme as default on the instance

[#1505] Restricted max thread distance for fetching replies on incoming federation (in addition to reply-to depth restriction).

Closes: https://git.pleroma.social/pleroma/pleroma/issues/1164

Ilja authored 5 years ago and Haelwenn committed 5 years ago

* Added "Migrate" to the title because these steps can also be used to migrate the instance to another server
* Added an optional step to reinstall pleroma (esp. for migrating servers)
* Currently the steps threw an error 'could not execute query: ERROR: function "activity_visibility already exists with the same argument types'
   * I added a new step to drop and recreate an empty pleroma-database
   * I played around with the `-c` and `-C` options of pg_restore, but dropping and recreating seemd to be the only way I got it working
   * This was tested on Debian Stretch, psql (PostgreSQL) 9.6.15

Large part of it was no longer true (i.e none of the changes need
recompilation anymore and you can't brick an instance by changing them,
it's not necessary to manually truncate the db manually anymore)