@[email protected] to [email protected]English • 8 months agoYour favorite lesser known docker container?message-square75fedilinkarrow-up1144
arrow-up1144message-squareYour favorite lesser known docker container?@[email protected] to [email protected]English • 8 months agomessage-square75fedilink
minus-square@[email protected]linkfedilinkEnglish1•8 months agoSo would this work well e.g. with the the *arr stack? Because most of the services wouldn’t even need to run always
minus-square@[email protected]linkfedilinkEnglish2•8 months agoIt 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.
minus-square@[email protected]linkfedilinkEnglish4•edit-28 months agoHow would the timed tasks be handled if they’re offline
So would this work well e.g. with the the *arr stack? Because most of the services wouldn’t even need to run always
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.
How would the timed tasks be handled if they’re offline