aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorzotlabs <mike@macgirvin.com>2018-06-17 21:13:46 -0700
committerzotlabs <mike@macgirvin.com>2018-06-17 21:13:46 -0700
commitdcd8fb289ee21536359998a64aeef2f4973834e3 (patch)
tree0b18b6eb785c83cdf882bced8403c2cd86c6d00a
parent0dc266153da954f5479979293f9fbd158ec0022e (diff)
downloadvolse-hubzilla-dcd8fb289ee21536359998a64aeef2f4973834e3.tar.gz
volse-hubzilla-dcd8fb289ee21536359998a64aeef2f4973834e3.tar.bz2
volse-hubzilla-dcd8fb289ee21536359998a64aeef2f4973834e3.zip
remove admin docs on upgrading from redmatrix; operation is no longer supported
-rw-r--r--doc/admin/administrator_guide.md10
1 files changed, 0 insertions, 10 deletions
diff --git a/doc/admin/administrator_guide.md b/doc/admin/administrator_guide.md
index 34dfa8cad..5f1d40428 100644
--- a/doc/admin/administrator_guide.md
+++ b/doc/admin/administrator_guide.md
@@ -331,16 +331,6 @@ empty:
util/config system directory_server ""
-### Upgrading from RedMatrix to $Projectname
-
-#### How to migrate an individual channel from RedMatrix to $Projectname
-
-1. Clone the channel by opening an account on a $Projectname hub and performing a basic import (not content) from the original RedMatrix hub. Give your new clone time to sync connections and settings.
-1. Export individual channel content from your RedMatrix hub to a set of JSON text files using the red.hub/uexport tool. Do this in monthly increments if necessary.
-1. Import the JSON data files sequentially in chronological order into the $Projectname clone using the new.hub/import_items tool.
-1. Inform your Friendica and Diaspora contacts that your channel moves. They need to reconnect to your new address.
-1. After successful import (check!) delete your channel on the old RedMatrix Server.
-1. On the $Projectname server visit new.hub/locs and upgrade to your channel to a primary one. And when the old Redmatrix server is still listed delete them here as well. Press "Sync" to inform all other server in the grid.
### Administration