-
Notifications
You must be signed in to change notification settings - Fork 246
Home
This documentation outlines how to run and configure FediFetcher:
-
Regardless of how you want to run FediFetcher, you must first get an access token:
Getting an Access Token for FediFetcher -
Once you have to your access token, there are multiple ways of running FediFetcher. None of these require you to have CLI/SSH access to your mastodon server. Pick one of the following options:
-
Running FediFetcher as a cron job
Ideal if you already have a linux device, and want to simply run FediFetcher on there. -
Running FediFetcher from a container
Ideal if you are familiar with containers. -
Running FediFetcher as a systemd timer
Ideal if you have a linux device somewhere, but don't like cron jobs. -
Running FediFetcher as a Scheduled Task in Windows
Ideal if you are a Windows User and your main device is (almost) always running.
-
Running FediFetcher as a cron job
Important
Running FediFetcher as GitHub Action is deprecated since May 2025. If you are running FediFetcher as GitHub Action it will cease running by 20th June.
If you are currently running FediFetcher as GitHub Action please see Migrating From GitHub Actions for migration details.
-
Configure FediFetcher:
FediFetcher has quite a few configuration options, so here is my quick configuration advice, that should probably work for most people:{ "access-token": "Your access token.", "server": "your.mastodon.server", "home-timeline-length": 200, "max-followings": 80, "from-notifications": 1 }
To find all available configuration options, read FediFetcher configuration options
-
It's really important you keep FediFetcher up to date. Please check the Updating FediFetcher documentation, for details on how to be notified of new releases, and how to install updates.
-
Want to contribute? Amazing! Have a look at Contribute To FediFetcher
Fork it and send a pull request. Read Contributing to FediFetcher for more info.