23b6f92c-43e1-4e11-aad1-7d8f6ae0f126

duplicate the service within the same project so its not as messy? and then as long as theres no need for a volume it should work relatively fine

the more complicated way to do it that would work even with a volume would be to add code to trigger the script when a certain endpoint is hit and then use other services (or even railway with a simple curl service?) that allow hitting an endpoint on a cron schedule

I actually think that's what I mean, duplicate service within the project.

It'd not need a volume, not need external web access, I have since noticed I can take the cores and stuff right down too

I did consider some sort of external Cron too but it felt more effort. I think I'll go with the duplicate service for now and just keep an eye on usage!

fun fact, you can duplicate the service via the service's right click context menu

Didn't know that either i went the long way 🫡

the context menu has some good stuff!

just on this, if i want something that needs to run on like a minute schedule - say for checking for scheduled posts, and kicking them off, im guessing cron builds with the start command as a script at that interval might be silly, and i should look to some other external cron service, w/ a webhook or smth?

daily felt fine but minute feels dirty

or i could turn off serverless and use node-cron

hello,

slight misunderstanding, we do not rebuild or redeploy on whatever the set schedule may be, we are simply starting the already built image again.

but even so, the minimum frequency you can run crons on is 5 minutes, so if you need anything with a higher frequency then you would need to move to an in-code scheduler like node-cron or equivalent.

thank you\

!s