Move remote pruning note over to 0.11
This commit is contained in:
parent
110a5e64dc
commit
aa39ef0571
|
@ -52,17 +52,6 @@ or use the image name ``jointakahe/takahe:0.10``.
|
|||
Upgrade Notes
|
||||
-------------
|
||||
|
||||
Remote Pruning
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
Post pruning is now in and comes *enabled by default*, as it is not directly
|
||||
destructive (it will only delete content that has not been interacted with
|
||||
locally and which can be re-fetched).
|
||||
|
||||
Nevertheless, if you want to avoid post deletion triggering on your server at
|
||||
all, you should set the ``TAKAHE_REMOTE_PRUNE_HORIZON`` environment variable to
|
||||
``0``.
|
||||
|
||||
Migrations
|
||||
~~~~~~~~~~
|
||||
|
||||
|
|
|
@ -9,6 +9,17 @@ Notes TBD.
|
|||
Upgrade Notes
|
||||
-------------
|
||||
|
||||
Remote Pruning
|
||||
~~~~~~~~~~~~~~
|
||||
|
||||
Post pruning is now in and comes *enabled by default*, as it is not directly
|
||||
destructive (it will only delete content that has not been interacted with
|
||||
locally and which can be re-fetched).
|
||||
|
||||
Nevertheless, if you want to avoid post deletion triggering on your server at
|
||||
all, you should set the ``TAKAHE_REMOTE_PRUNE_HORIZON`` environment variable to
|
||||
``0``.
|
||||
|
||||
VAPID keys and Push notifications
|
||||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
||||
|
||||
|
|
Loading…
Reference in New Issue