undefined | Better HN

0 pointsMontyCarloHall2mo ago0 comments

>Instead of installing a container manager or using Unix users, just make another VM.

What is the advantage of this? Unless you need something exotic like different kernel configurations per instance, what's the problem with using containers on the same instance?

BTW, a Hetzner dedicated server with 2 CPUs/8GB RAM that would let me run my own hypervisor is about $14 USD/month. For anyone who's a big enough power user to care about the distinction of running distributed workflows on VMs versus containers, I'm not sure that an extra $5/month is worth your "hypervisor as a service." But then again, HN commenters infamously poopooed Dropbox [0], so what do I know? :-)

[0] https://news.ycombinator.com/item?id=9224

0 comments

crawshaw2mo ago

Containers aren’t enough for me. I like to do things like create TUN devices, run docker compose, etc. I believe the VM is a fundamentally better abstraction.

Consider this: sometimes when you are using a VPS, you start a new project and say to yourself, "I should put this on a new VPS." Not all the time, but it does happen. And when it does, we are faced with the problem that starting a new project immediately costs us $X/month. I would like a new project to initially cost nothing.

Kwpolska2mo ago

> create TUN devices

Is that possible and useful with exe.dev? The docs say:

On the networking side, we don't give your VM its own public IP. Instead, we terminate HTTPS/TLS requests, and proxy them securely to your VM's web servers. For SSH, we handle ssh vmname.exe.xyz.

> run docker compose

You can run multiple compose stacks in a single VPS.

> you start a new project and say to yourself, "I should put this on a new VPS."

I never did that.

crawshaw2mo ago

Tun devices are possible and useful on exe.dev today, because it means, for example, you can install the full copy of Tailscale.

But to your point: if a single VPS meets all your needs and you do not feel constrained by the marginal cost of another VPS then the exe pricing model is not going to bring you much value. Perhaps the automatic TLS termination and auth proxy with link sharing is useful. But if not, then it sounds like you are well served by existing products.

danecjensen2mo ago

Is exe.dev just a better version of sketch.dev or do they both have a different use case?

j / k navigate · click thread line to collapse

0 pointsMontyCarloHall2mo ago0 comments

>Instead of installing a container manager or using Unix users, just make another VM.

What is the advantage of this? Unless you need something exotic like different kernel configurations per instance, what's the problem with using containers on the same instance?

[0] https://news.ycombinator.com/item?id=9224

0 comments

crawshaw2mo ago

Containers aren’t enough for me. I like to do things like create TUN devices, run docker compose, etc. I believe the VM is a fundamentally better abstraction.

Kwpolska2mo ago

> create TUN devices

Is that possible and useful with exe.dev? The docs say:

On the networking side, we don't give your VM its own public IP. Instead, we terminate HTTPS/TLS requests, and proxy them securely to your VM's web servers. For SSH, we handle ssh vmname.exe.xyz.

> run docker compose

You can run multiple compose stacks in a single VPS.

> you start a new project and say to yourself, "I should put this on a new VPS."

I never did that.

crawshaw2mo ago

Tun devices are possible and useful on exe.dev today, because it means, for example, you can install the full copy of Tailscale.

danecjensen2mo ago

Is exe.dev just a better version of sketch.dev or do they both have a different use case?

j / k navigate · click thread line to collapse