0
0
Fork 0

Adding sort by node rank to follow suggestions and fallback to most influential users

This commit is contained in:
Eugen Rochko 2016-10-15 16:43:52 +02:00
parent 492a682e34
commit 7075cef8f9
3 changed files with 48 additions and 4 deletions

View file

@ -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: