about summary refs log tree commit diff
path: root/README.md
diff options
context:
space:
mode:
authorAndrea Faulds <ajf@ajf.me>2016-11-26 16:35:37 +0000
committerAndrea Faulds <ajf@ajf.me>2016-11-26 16:35:37 +0000
commit1c9c176beca9fd638e2521961d1c27953b697cbd (patch)
treef38d5d1232dfbe565b7bc225006399cf9e875136 /README.md
parentb107a4820ad44ccd1944a83419ea48b81ba672b7 (diff)
Remove another lingering Neo4J item
Diffstat (limited to 'README.md')
-rw-r--r--README.md1
1 files changed, 0 insertions, 1 deletions
diff --git a/README.md b/README.md
index 4ffa9f619..304e37935 100644
--- a/README.md
+++ b/README.md
@@ -89,7 +89,6 @@ The container has two volumes, for the assets and for user uploads. The default
 - `rake mastodon:push:clear` unsubscribes from PuSH notifications for remote users that have no local followers. You may not want to actually do that, to keep a fuller footprint of the fediverse or in case your users will soon re-follow
 - `rake mastodon:push:refresh` re-subscribes PuSH for expiring remote users, this should be run periodically from a cronjob and quite often as the expiration time depends on the particular hub of the remote user
 - `rake mastodon:feeds:clear` removes all timelines, which forces them to be re-built on the fly next time a user tries to fetch their home/mentions timeline. Only for troubleshooting
-- `rake mastodon:graphs:sync` re-imports all follow relationships into Neo4J. Only for troubleshooting
 
 Running any of these tasks via docker-compose would look like this: