Mine is beaverhabits, just a good habit app that has come out recently.

  • BrianTheeBiscuiteer@lemmy.world
    link
    fedilink
    English
    arrow-up
    24
    ·
    25 days ago

    Not useful on its own but https://sablierapp.dev/ was really useful for me in getting back resources from some of the heavyweight containers I use. For those unfamiliar with it, Sablier can stop containers that go idle and then spin them back up automatically when a request comes in. It requires Traefik, NGINX, or Caddy running always so it could complicate your server but for me I couldn’t do without it.

    • shaserlark@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      1
      ·
      24 days ago

      So would this work well e.g. with the the *arr stack? Because most of the services wouldn’t even need to run always

      • BrianTheeBiscuiteer@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        24 days ago

        It probably would work well with those as long as the startup time was quick (my containers come up almost instantly) and the initiating clients can handle a bit of latency. I didn’t notice any hiccups in my use at all.

    • filcuk@lemmy.zip
      link
      fedilink
      English
      arrow-up
      1
      ·
      24 days ago

      I believe this can integrate with various reverse proxies and trigger on-demand?

      • BrianTheeBiscuiteer@lemmy.world
        link
        fedilink
        English
        arrow-up
        2
        ·
        edit-2
        24 days ago

        Right. When a request comes in, Traefik, for one, will hold the connection until the service is back up then forward the request as usual. This works for UIs as well. You’ll get a temporary loading page then redirected to the requested UI when the service is up.