Live data from Hacker News

Exe.dev

exe.dev

251–260 of 316 posts

Re: Exe.dev

#251
post #209

Earlier quoted context omitted.

tbh maybe this service doesn't want you as a customer if you can't figure this out. it seems like you'd be an above-average support burden

Are you honestly suggesting that startups should be picky about taking on customers? That’s probably the oddest thing to read on a tech VC forum. The lading page was garbage. It’s forgivable because designing goods landing pages is hard. But inventing wacky ideas about why a bad landing page might have some hidden genius, isnt constructive feedback

Why are you giving in to such a troll/AI/low effort comment. If the page was some genius implication and I were too stupid to get it then his comment had a good point. The page has a random ssh command and this dude thinks it's genius.

Re: Exe.dev

#252

Earlier quoted context omitted.

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…

> 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 ne…

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.

Re: Exe.dev

#253
i tried this and it's pretty cool, that being said for my use case of spinning up many agents working on my app I'd need a way to specify the docker images that get started with each new VM

i cannot find a way in the docs to start new VMs with a bootstrap script that starts a bunch of services for me and runs a specific docker image

my use-case is that I want a full developer environment for every branch of my project, so i can vibe code on many VMs at a time

EDIT: Just realised there's an image one can pass to the new command. Still it's not clear to me whether private images would be supported and what registry this is using:

exe.dev ▶ help new

Command: new

Create a new VM

Options: --command container command: auto, none, or a custom command --env environment variable in KEY=VALUE format (can be specified multiple times) --image container image --json output in JSON format --name VM name (auto-generated if not specified) --no-email do not send email notification --prompt initial prompt to send to Shelley after VM creation (requires exeuntu image)

Re: Exe.dev

#254
post #216

Earlier quoted context omitted.

No I apologize for the confusion (exe.dev person here). What is different about this service is you get dedicated resources that you share between your VMs. The initial allocation is conservative, we want to give people more (or drop the price). The goal is to reduce the marginal cost of creating a VM to zero. Instead of installing a container manager or using Unix users, just make another VM. (I will get a better ve…

Is rsync installed in the stock vm environment by default? Asking for a friend…

[exe.dev co-founder here]

  exedev@scarlet-canyon:~$ rsync --version
  rsync  version 3.2.7  protocol version 31                                         
  Copyright (C) 1996-2022 by Andrew Tridgell, Wayne Davison, and others.
Our base image is most of an Ubuntu server. We trim out, for example, systemd features that are designed for working with system hardware, and then add a lot of standard software, as our block device cloning is a lot faster and more efficient than apt. So you will find vim, git, go, curl, sqlite3, etc all installed. If you think something obvious is missing please let us know!

Re: Exe.dev

#255
post #216

Earlier quoted context omitted.

Is rsync installed in the stock vm environment by default? Asking for a friend…

[exe.dev co-founder here] exedev@scarlet-canyon:~$ rsync --version rsync version 3.2.7 protocol version 31 Copyright (C) 1996-2022 by Andrew Tridgell, Wayne Davison, and others. Our base image is most of an Ubuntu server. We trim out, for example, systemd features that are designed for working with system hardware, and then add a lot of standard software, as our block device cloning is a lot faster and more efficient…

Would love it if Tailscale came pre-installed! Or even better: some simple way to make it so every VM I start up is automatically/easily part of my Tailnet.

p.s. thanks for making Tailscale. And I'm loving exe.dev so far!

Re: Exe.dev

#257
I normally try to stick to serverless with SST for quick projects because I like that they scale to $0, but this is enticing. Shelley is a great feature and must have well-designed system prompts and tools for testing the website built-in. It just one-shotted a volunteer management app and with just one more click in the console I can expose it to the public.

Re: Exe.dev

#258
post #211
post #193

Earlier quoted context omitted.

Yeah, and it really is not I would want to do, just like diving into unknown water that sparkles weird.. It's an instinct, can get past it but to get more info about the service... nah.

That's okay, you're not in the target audience is all.

If their target audience is someone who remotes into a random machine because a opaque landing page them to, it's probably not gonna work very well. Those people are too busy sniffing glue.

Re: Exe.dev

#259
post #100

Earlier quoted context omitted.

> I almost immediately surmised it's some sort of on the fly generated vm you can access via a ssh jumpserver How? It just says `ssh exe.dev`. Unless you are clairvoyant.

You are not the target audience if "how" was not apparent to you

The "how" is very obvious, but not the "why". I'd assume this much would be very apparent from the OPs complaint, but apparently not I guess...

Re: Exe.dev

#260
This is very cool, but goodness I wish they'd give an option for a password-based login after the initial verification. In ~10 minutes of playing with it I had to go through 4 email confirmation steps.

I'm very much into the product itself, but that would get extremely tiresome if I was trying to use it consistently. I assume I have to be using it wrong in some way for there to be that much friction...

Post reply on HN