-
Notifications
You must be signed in to change notification settings - Fork 235
Running FediFetcher as a GitHub Action
Running FediFetcher as a GitHub Action is probably the simplest way of running FediFetcher if you don't have Linux admin experience. You do not need any 'server' or other hardware to use GitHub Actions, as everything runs on GitHub's servers.
The disadvantage is that you have limited control over this, and that you cannot run FediFetcher more frequently than every 10/15 minutes.
Important
When running FediFetcher as GitHub Action you will need to confirm that you want to keep running FediFetcher approximately every 60 days. GitHub will send you an email with instructions when required.
To run FediFetcher as a GitHub Action:
- Get an Access Token, if you haven't done so already
- Fork this repository
- Add your access token as a Secret:
- Within your newly created fork, go to Settings > Secrets and Variables > Actions
- Click New Repository Secret
- Supply the Name
ACCESS_TOKENand provide the Token generated above as Secret
- Create a file called
config.jsonwith your configuration options in the repository root. Do NOT include the Access Token in yourconfig.json! - Finally go to the Actions tab and enable the action. The action should now automatically run approximately once every 10 min.
Caution
Do not include the access-token in the config.json when running FediFetcher as GitHub Action. When running FediFetcher as GitHub Action ALWAYS set the Access Token as an Action Secret, as described above. If you have accidentally saved the token in the config.json, consider it compromised and regenerate it immediately.
Note
Keep in mind that the schedule event can be delayed during periods of high loads of GitHub Actions workflow runs.
It's important to stay up to with FediFetcher so you always get the latest features and bugfixes.
Please refer to the Updating FediFetcher documentation for more information.
Fork it and send a pull request. Read Contributing to FediFetcher for more info.