@iKill101
@lemmy.bleh.auAs per title.
Wondering if anyone else here has had any experience with the self-hosted version of OneUptime? And specifically, has anyone had any luck setting it up behind Nginx Proxy Manager?
I've managed to set it up, but I'm honestly not 100% happy with how you have to essentially have two servers to host it (one being a reverse proxy for the admin interface, the other being the application core).
Don't get me wrong, it's neat and definitely full featured, but there is still a long way to go with it. For my use case, I wanted a public status page that people can subscribe to for updates. I'd come from UptimeKuma which was fantastic but lacked the subscriber feature. I used to use Cachet back in the day before it became abandonware (the original owner bought the rights back for it and has rebooted development for it, though!).
https://external-content.duckduckgo.com/iu/?u=https://media1.giphy.com/media/l41m4ODfe8PwHlsUU/giphy.gif&f=1&nofb=1&ipt=ecd7fe8e53bb59b1e80622a3af1cb89b45f34aefcc6d0d93411d768ca9c03e45&ipo=images
Unfortunately, some people have decided to post CSAM on remote instances. The moderators of the communities have been very proactive, but because of the federated nature of Lemmy, it means the material had federated.
So like most instances are doing, we've initiated a purge on the pictrs database/filesystem to delete ALL images from the last 24 hours.
Images may appear broken. I'd like to apologise for the inconvenience, but as Lodion said best on his post in !meta@aussie.zone - "... this is pretty much the nightmare scenario for an instance. I’d rather nuke all images ever than to host such content."
It's pretty disgusting.
For fellow Lemmy admins who are curious, the script to delete is:
sudo find /srv/lemmy/example.com/volumes/pictrs/files -type f -ctime -1 -exec shred {} \;
Be sure to modify the path to point to your pictrs directory!