by indoorskier on 6/10/22, 2:37 PM with 20 comments
by indoorskier on 6/10/22, 2:39 PM
We're two programmers who have worked in core/platform engineering roles for most of our working lives. During that time, one of the main problems we've solved time and time again is to let people run their ad-hoc jobs and scripts on remote compute without hassle.
To solve this once and for everyone, we made Meadowrun, an open source tool that automates the tedious details of running Python code on cloud VMs. It runs in your AWS or Azure account, nothing else required.
No need to mess around with containers, SSH into remote machines, copy code across, set up images or look up instance types that sound like Starbucks orders ("t3.venti.oatmilk.latte") and what they cost.
All with the same experience as you'd have running on your laptop - just change the code or dependencies locally and run - meadowrun takes care of the rest.
We welcome any and all feedback!
by sscarduzio on 6/12/22, 7:26 AM
Another signal of cloud rot: I see myself and my peers are migrating away from AWS to smaller, less complicated, cheaper providers like Linode, but also Hetzner, Wasabi.
Nowadays the cloud fatigue is higher than the burden of self hosting your services.
by danbmil99 on 6/11/22, 12:44 AM
https://news.ycombinator.com/item?id=28191450
We got quite a few comments on hacker news but unfortunately we didn't see a lot of uptake.
by garyrob on 6/10/22, 10:09 PM
[1] http://pywren.io
by barefeg on 6/10/22, 7:11 PM
by nathants on 6/10/22, 7:24 PM
i4i instances recently launched. so much fast local disk. so much bandwidth to s3. needs more data processing.
subscribing to the commits on github.
by focom on 6/10/22, 5:38 PM