diff options
| author | Eugen Rochko <eugen@zeonfederated.com> | 2016-10-15 16:43:52 +0200 |
|---|---|---|
| committer | Eugen Rochko <eugen@zeonfederated.com> | 2016-10-15 16:46:15 +0200 |
| commit | 7075cef8f99f715fbf77a67e45bbc1e7edcada42 (patch) | |
| tree | e2db2fa465489effb8d19cb06b649bd990e18d56 /README.md | |
| parent | 492a682e34d66dd3046ed08f7aee80fb5317f777 (diff) | |
Adding sort by node rank to follow suggestions and fallback to most influential users
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/README.md b/README.md index aa5801c5d..0ca699212 100644 --- a/README.md +++ b/README.md @@ -57,6 +57,8 @@ Consult the example configuration file, `.env.production.sample` for the full li - PostgreSQL - Redis +- Neo4J (optional) + - GraphAware NodeRank ## Running with Docker and Docker-Compose @@ -86,6 +88,7 @@ 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: |