this post was submitted on 30 Jul 2023
1057 points (98.3% liked)
Lemmy.World Announcements
29084 readers
154 users here now
This Community is intended for posts about the Lemmy.world server by the admins.
Follow us for server news ๐
Outages ๐ฅ
https://status.lemmy.world/
For support with issues at Lemmy.world, go to the Lemmy.world Support community.
Support e-mail
Any support requests are best sent to info@lemmy.world e-mail.
Report contact
- DM https://lemmy.world/u/lwreport
- Email report@lemmy.world (PGP Supported)
Donations ๐
If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.
If you can, please use / switch to Ko-Fi, it has the lowest fees for us
Join the team
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
It's really great that you are moving so quickly and supporting your community in this way, but I wonder if all these front ends are potentially going to create a bit of a long term maintenance headache? How are we certain that they don't introduce any new vulnerabilities and how are we staying on top of those when they happen? I worry that each new frontend adds burden to an already small community for a potentially minor practical gain.
Don't get me wrong, you guys are doing awesome stuff, and I'm consistently impressed with this instance. That's just the first thing that comes to my head having done software for many years myself.
Maintenance in regards to updates is not an issue. All the extra frontends we added run in docker and are automatically updated twice a day to make sure we are always running the latest stable versions. All apps are using the Lemmy api's just like the 3rd party apps and should anything break we have ways to contact the developers.
How did you set them up to automatically update? Have you done a write up on how you set these up? Would be great for other admins to be able to do the same
We use docker compose in scripts and crontabs
/scripts/update-alexandrite.sh:
Then use crontab -e and add this line:
00 05,00 * * * bash /scripts/update-alexandrite.shAre you concerned at all with auto updating containers that some updates can break stuff?
Iโve had issues with watchtower and auto updating containers in the past breaking config files and stopping containers.
Changing the update rate in cron can help offset any broken / vulnerable updates that get pushed.
Sweet thanks, do you have this and scripts to keep the other front ends updated on GitHub somewhere?
It's just docker compose and crontab..
I understand but a lot of admins that are hosting instances just for themselves and a couple of friends have little no experience running a server so having a github with different tips and best practices would be very useful. I hope you consider it :)