Moving GetMoarFediverse over to my own Infrastructure - Mastodon
I wrote two days ago about moving FediFetcher over to my own infrastructure (away from GitHub Actions and over to my Synology NAS at home).
Getting this onto my Synology is actually pretty darn easy,
From my FediFetcher post, I will be using the
~/Mastodon folder to hold everything.
First, I need to download the executable from the project’s GitHub repo. I don’t have much patience to compile it myself, and I trust the developer.
- Repo: https://github.com/g3rv4/GetMoarFediverse
- Executibles: https://github.com/g3rv4/GetMoarFediverse/releases
At the time of writing, I downloaded version 1.0.54, the latest version.
This places the executable
GetMoarFediverse in the folder
I do a simple simlink so I don’t need to worry about paths in the future when I upgrade.
This allows me to run the executable from the path
/var/services/homes/cdrum/Mastodon/GetMoarFediverse (Your paths may be different depending on how your Synology DSM is set up, and the username, etc.)
Next, the confguraton. I took the config I had from my GitHub Action repo (that was cloned from GMFActionDemo):
And I pasted the contents into a new json file I put in
/var/services/homes/cdrum/Mastodon that I called
getmoarfediverse-config.json (a bit long, I know).
I then need to add another entry
"FakeRelayApiKey": and use the FakeRelay api key I got earlier, so the file now looks like:
(replace “blahblahblah” with your key!)
Then, I can simply run it one time manually by running the following:
If all goes well, you’ll see a lot of output pulling in toots that match your settings. Example:
Setting up the Cron
Going back to the Synology DSM Interface, go to the Task Scheduler
Then fill out the various pages. give it a name:
Configure the schedule (I chose every 5 minutes)
And finally configure the taks settings it self. Paste in the following string in the User-defined script field:
/var/services/homes/cdrum/Mastodon/GetMoarFediverse/GetMoarFediverse /var/services/homes/cdrum/Mastodon/getmoarfediverse-config.json >> /var/services/homes/cdrum/Mastodon/getmoarfediverse-cron.log 2>&1
Notice I added the
>> /path_to_log so I can check the log from time to time to make sure it runs. (Note: do check on the file size from time to time. It will grow quite large.)
Click OK and let’s see if it works!
You sholuld be able to tail the log file to make sure all is working correctly.
tail -f getmoarfediverse-cron.log
Then as you want to make changes to your hashtags and/or mastodon instances, simply edit the ..config.json file, and the next cron run should pick up the changes.
Hope this helps!