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 @stefan thank you for the heads up! do I put that code on the same line as the cron job instructions?

@_elena

Yes, like this:

0 5 * * * bash ~/backups/backup.sh > /dev/null 2>&1

which runs mybackup at 5am each day.  You just need to be confident that your script has no errors, as you will never see them!  Or ensure your script outputs to a log of its own within the script

@stefan

@_elena @stefan
@daj

Of course, if you need/want a log to see why the script fails you can temporarily send the log wherever you want like ~/mylogs/cronlogs/oh-no.log (or permanently)

And later you can learn about logrotate to keep a certain amount of logs but not let it grow forever and fill up your drive.