3 ms·
It's reasonable to call this the "easiest" way. It's certainly not the "cheapest, easiest" way, which is what the poster asked for. Many of the other options l
by akerl_ 4y ago
It's reasonable to call this the "easiest" way. It's certainly not the "cheapest, easiest" way, which is what the poster asked for.
Many of the other options listed in this thread are free or within a rounding error of free. Some of them equally are not the "cheapest, easiest" because they're complex. But some of them pretty clearly meet both criteria (GitHub Actions comes to mind), and some of them might meet the criteria depending on what somebody has familiarity with (if you're already used to deploying code to any FaaS provider with a free tier, that'll likely be the cheapest/easiest way).
- ryandrake 4y agoThe way I look at it: If you have an existing VPS already hosting things (and what geek doesn't?) then adding a cronjob to that host incrementally costs essentially $0 and is pretty much the easiest thing you can do.
- akerl_ 4y agoJust to say it out loud: there are plenty of geeks w/o a VPS, either because they hack on things that don't generally need a server (like hardware, or radio, or any number of other geek pursuits) or because they've historically used local gear for their compute tasks. If you have a VPS, I agree, adding a cronjob to it is both cheap and easy. But it's silly to assume that anybody who is a geek has a VPS already.
- hagbarth 4y agoAs one of the sibling comments points out, you could set this up on a GCP free tier VM.