• 0 Posts
  • 37 Comments
Joined 1 year ago
cake
Cake day: June 11th, 2023

help-circle




  • so I assumed someone would probably have subscribed before me

    I think the community is very new, so there’s a decent chance you were the first. As to the overloading problem, it’s certainly possible. Lemmy.world has a ton of users, and while I know ruud is dedicating a lot of resources to your lemmy instance, it just may not be enough to keep performance great. There’s been a lot of reports of performance problems by both lemmy.world users and federation problems between .world and other lemmy instances, most likely from being overloaded. You might try setting up a secondary account on another instance if you’re inclined, can’t hurt. Then at least you’ll be able to compare. Mine is on sh.itjust.works and everything has been pretty decent for me since the latest software upgrade, just as a point of reference.

    Sorry for my cluelessness, I’m new to the fediverse

    No worries mate, we’re all new here. I’m still getting used to things too.



  • how can that be if others from this instance have already subscribed?

    How certain are you that the community was already subscribed to? You may be the first person on your instance to subscribe there. If that’s the case you’ll only be seeing anything posted after you subscribed.

    That is, unless Faceman is correct, in which case lemmy.world will eventually backfill content when it can.

    For example, I’m seeing three posts there on both my instance and when I visit https://feddit.nl/c/trendingcommunities. I’m fairly sure that when I first subscribed I could only see the first post, but definitely not sure that’s the case.





  • The way I have my monitoring set up is to poll the containers from behind the proxy layer. Ex. if I’m trying to poll Portainer for example:

    ---
    services:
        portainer:
        ...
    

    with the service name portainer

    from uptime-kuma within the same docker network it would look like this:

    Can confirm this is working correctly to monitor that the service is reachable. This doesn’t however ensure that you can reach it from your computer, because that depends on if your reverse proxy is configured correctly and isn’t down, but that’s what I wanted in my case.

    Edit: If you’re wanting to poll the http endpoint you would add it before like http://whatever_service:whatever_port


  • I believe the Pictrs is a hard dependency and Lemmy just won’t work without it, and there is no way to disable the caching

    I’ll have to double check this but I’m almost certain pictrs isn’t a hard dependency. Saw either the author or one of the contributors mention a few days ago that pictrs could be discarded by editing the config.hjson to remove the pictrs block. Was playing around with deploying a test instance a few days ago and found it to be true, at least prior to finalizing the server setup. I didn’t spin up the pictrs container at all, so I know that it will at least start and let me configure the server.

    The one thing I’m not sure of however is if any caching data is written to the container layer in lieu of being sent to pictrs, as I didn’t get that far (yet). I haven’t seen any mention that the backend even does local storage, so I’m assuming that no caching is taking place when pictrs is dot being used.

    Edit: Clarifications


  • Thanks for sharing! I’ll definitely be looking into adding this to my infra alerting stack. Should pair well with webhooks using ntfy for notifications. Currently just have bash scripts push to uptime-kuma for disk usage monitoring as a dead man trigger, but this should be better as a first-line method. Not to mention all the other functionalities it has baked in.

    Edit: Would also be great if there was an already compiled binary in each release so I can use bare-metal, but the container on ghcr.io is most-likely what I’ll be using anyway. Thanks for not only uploading to docker hub.