v5.0.0

Change log

• Configuration has been simplified and unified into a json file for GitHub Actions and local execution. This is a breaking change for users of GitHub Actions (#49, #51)
• Accept incorrect provision of server url instead of server host (9edbee7)

Sample config file

{
  "access-token": "Your access token",
  "server": "your.mastodon.server",
  "home-timeline-length": 200,
  "max-followings": 80,
  "from-notifications": 1
}

Warning
Do NOT include your 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!

Update instructions

If you are running from Git Hub Actions

No update is needed immediately, but if and when you want to update your fork (e.g. to make use of any new configuration options introduced in the future, or to incorporate bug fixes), you will need to switch to the new, json based configuration.

If you wish to switch to the new json file based configuration:

1. Update your fork
2. Create a config.json file in the repository root, and provide the desired configuration options.

Note
The option previously known as MASTODON_SERVER is now server. All other configuration option names are unchanged.

Warning
Do NOT include your access-token in the config.json when running FediFetcher as GitHub Action.

If you are running locally

Switching to the new json file based configuration is and will continue to be optional. You will continue to be able to use command line flags for both new and existing configuration options.

If you wish to switch to the new json file based configuration:

1. Update your fork
2. Create a config.json file (e.g in the ./artifacts directory, and provide your configuration options in there
3. Call your script with the --config=./artifacts/config.json directive instead of the existing command line flags.