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

  • @BrianTheeBiscuiteer
    link
    English
    222 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.

      • @BrianTheeBiscuiteer
        link
        English
        2
        edit-2
        15 hours 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.

    • @[email protected]
      link
      fedilink
      English
      11 day 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

      • @AustralianSimon
        link
        English
        4
        edit-2
        1 day ago

        How would the timed tasks be handled if they’re offline

      • @BrianTheeBiscuiteer
        link
        English
        21 day 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.