My experience of the #fediverse :

Year 1 (2023):
It feels a little lonely as 99% of my friends stayed on Big Tech platforms.

Year 2 (2024):
I start a blog - #TheFutureIsFederated - to explain the fediverse to "normies"... and I make a lot of new (techie) friends.

Year 3 (2025):
My techie friends encourage me to start self-hosting with #YunoHost... and I do! (GoToSocial, PeerTube, NextCloud...) I LOVE it.

Year 4 (2026):
I plan to buy a Heltec to try out off-grid mesh radio communication 💁‍♀️

About to create my first cron job. Wish me luck! 😅

#MySoCalledSudoLife #SelfHosting

@_elena cronjobs are the best. all my bots depend on them! very reliable!

one thing that got me early on: any output from a script ran in a cronjob seems to be put in some log file. Left alone that log file can fill all the space in your system.

for reasons I don't fully understand this line fix that by stopping the logging:

MAILTO=""

@stefan

I add the following at the end of the cron job

' > /dev/null 2>&1 '

Ignore the ' at start and end. Can't get my markdown to show as code

It captures ALL output from STDOUT and STDERR and sends it to /dev/null (that is, nowhere)

@_elena

@daj @_elena

for me the cronjob is a file I edit by calling "crontab -e" on my server.

so I then put MAILTO="" on it's own line.

What david is suggesting also sound good / better!

@stefan I'm intrigued what MAILTO in this context does.  I must dig deeper. Every day is a school day
@daj i found it on stackoverflow years ago and didn't investigate deeply. but has worked well for me!