Hacker News new | ask | show | jobs
by gdcbe 992 days ago
I use shuttle to deploy some side Rust projects for my web facing parts. I love it.

They are also planning to allow you to host it yourself via a docker setup, in your basement or cloud. For now I’m just doing it via their service and gladly pay for it.

If you’re well versed into DevOps related activities you might find it odd that there’s a need for it. But personally I’m a father of 3 kids, have been a developer and and hacker for last 12 years or so, and while I could do AWS, gcloud or a VPS myself, I honestly rather spend that time on my product then infra worries. So far I haven’t experienced any issues with them and they are very friendly folks, always ready to help. They’ll also be at EuroRust next week.

If you’re like me someone who likes to develop stuff but not so much the deployment side of things, then honestly this is nice.

There’s honestly no lock-in:

1. You’re service (project) can easily be converted into a regular project, as shuttle is in code only visible in a minimal way, so you can fairly easily refactor it out of your project the day you want to switch away 2. And like I said they’ll allow to self host soon enough.

So maybe you can give it a try. Might be the accelerator you need to help you start a project / business idea. Even if just to get you started.

2 comments

Is there a reason to use this over, say, Render?
No. It’s just another alternative. I’m not a web developer in my day job. So I’m not aware of all options out there.

Render does look awesome. More mature and all. It’s not as easy as shuttle though.

- shuttle comes with a cli that allows you to run your app in similar fashion as the cloud version

- with shuttle you don’t need to configure the storage (eg db) and such yourself

That said. The price you pay is tighter coupling to the system. On top of that Render looks a lot more mature.

For now I’ll stick with shuttle for those projects. But I do thank you for telling me about render. Might switch to it, away from shuttle, if I my project’s needs ever outgrow shuttle’s capabilities

I'm wondering this same thing - my current assessment is no and that a YAML config is superior to compile-time macros. If I used Shuttle, I'd probably be using cfg-if and type aliases anyway to stop it from infecting the majority of my code. The proposed benefit of having a compile-time validated config is not a tangible one in my opinion. I don't think the abstractions are that beneficial either.

This is kind of a harsh assessment, but maybe it's just not for me.

I'm using mypaas and can have no worries + VPS.