ComradeMiao@lemmy.world to Selfhosted@lemmy.worldEnglish · 16 days agoYour favorite lesser known docker container?message-squaremessage-square70fedilinkarrow-up11arrow-down10file-text
arrow-up11arrow-down1message-squareYour favorite lesser known docker container?ComradeMiao@lemmy.world to Selfhosted@lemmy.worldEnglish · 16 days agomessage-square70fedilinkfile-text
minus-squareshaserlark@sh.itjust.workslinkfedilinkEnglisharrow-up0·16 days 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-squareBrianTheeBiscuiteer@lemmy.worldlinkfedilinkEnglisharrow-up0·16 days 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-squareAustralianSimon@lemmy.worldlinkfedilinkEnglisharrow-up0·edit-216 days 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