6 months ago
Are auto image upgrade schedules supposed to be set on a per service level or a project level? I have some services I don’t want to auto upgrade at the minute and others I do, but seems I can only set it per project as it changes it for all services when I make a change to any of the schedules
13 Replies
6 months ago
It is per service! If it changes like you mentioned it is a bug. I will fix soon
6 months ago
It is likely a UI issue if it is the same across services
Sussed it out, I was trying to play around on mobile, as soon as I got back to my macbook I figured the ‘save’ prompt is missing on mobile - so yeah UI bug on mobile hiding the prompt (you can’t scroll to it)
6 months ago
ahh thats not great. what phone/OS is it?
The new UI looks so much better & works great on mobile, thanks so much!
Hey! I can create another thread if needs be, but are you aware of any delays with auto updates? I have noticed times where a new package is released but the time between the release on ghcr and redeploy on Railway has been anywhere from 30mins-11hours after the release!
6 months ago
We have aggressive caching on checking for new image versions. It might be a bit too delayed and can look at decreasing it. It started high because we wanted to make sure we didn't have rate limit issues when fetching from ghcr/dockerhub apis
6 months ago
you can force an update through the command palette (cmd+k "check for image updates") and then if there are updates it will redeploy in <30min