[deleted]
Exe.dev
41–50 of 316 posts
Re: Exe.dev
#42The description of authentication mechanism is confusing me. it’s over ssh, but how is this integrated? > Private by default, share with discord-style links exe.dev takes care of TLS and auth for you. By default only you can reach your HTTP services, and you have easy mechanims to share them with friends and colleagues. Is anyone with access to a link able to get in?
You ssh in with any key, and it asks you for an email to verify. You're then at a exe.dev console. There are a couple different link patterns: exe.dev ▶ doc sharing Sharing (sharing) - press q to exit You can share your VM's HTTP port (see the http proxy documentation /proxy) with your friends. There are three mechanisms: 1. Make the HTTP proxy public with share set-public . To point the proxy at a different port ins…
Thanks! love the idea, looking forward to playing with this. I understand now from comments that this was brought to this site sooner than intended, sorry if I asked in a rude way.
Re: Exe.dev
#43Might be a good place for yunohost/coolify style services, especially if you have multiple separate entities - though probably tricky to do inbound mail because of IP allocation?
Re: Exe.dev
#44Earlier quoted context omitted.
Apologies for the vagueness of the home page, we were not expecting to be here today. There is a little more info in our first blog post https://blog.exe.dev/meet-exe.dev and docs, but far needs to be written. (We have also built some interesting tech behind this that we are excited to write up, I have a doc two pages long of blog posts we want to write.)
The blog doesn't work on Firefox on Android for me https://blog.exe.dev/meet-exe.dev Secure Connection Failed The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem.
I just tried this out in Firefox on macOS and there are no issues, so this might have something to do with our LetsEncrypt wildcard cert and the CA roots installed on Android. Could you tell me what version of Android you are using?
Re: Exe.dev
#45Are there any fundamental differences between E2B and this?
Hello, exe.dev person here.
I have not used E2B (though I really like their web site), though it looks like there are quite a few differences. Our disks are persistent (without manual snapshotting), we have a TLS proxy by default with built-in auth and link sharing.
It also looks like they have many features we do not have (yet).
I believe the target use is also quite different. You can use exe.dev VMs for running your agent. But you can also use it for hosting your site. E.g. blog.exe.dev is an exe.dev VM.
Re: Exe.dev
#46Oh I’m going to need more info than this. It’s a service that provides persistent disk and VM’s but doesn’t tell you what those shared resource limits are, what the pricing is, or anything other than to ssh in…
Hello, an exe.dev person here. There are some very early docs, exe.dev/docs (which are also accessible over ssh once you ssh in). There is a lot more to come, very early days, please bear with us. I was not expecting to see it here today.
I have played with it and it's so easy get started with that now I want a quick-project idea as an excuse to use it!
I'm sure you've thought of this, but: lots of people have some amount of 'free' (or really: zero incremental cost to users) access to some coding chat tool through a subscription or free allowance like Google's.
If you wanted to let those programs access your custom tools (browser!) and docs about the environment, a low-fuss way might be to drop a skills/ dir of info and executables that call your tools into new installs' homedirs, and/or a default AGENTS.md with the basic info and links to more.
And this seems like more fuss, but if you wanted to be able to expose to the Web whatever coding tool people 'bring', similar to how you expose your built-in chat, there's apparently an "agent control protocol" used as a sort of cross-vendor SDK by projects like https://willmcgugan.github.io/toad-released/ that try to put a nice interface on top of everything. Not saying this'd be easy at all, but you could imagine the choice between a few coding tools and auth info for them as profile-level settings pushed to new VMs. Or maybe no special settings, and bringing your own tools is just a special case of bringing your own image or setup script.
But, as y'all note, it's a VM. You can install whatever and use it through the terminal (or VSCode remoting or something else). "It's a computer" is quite a good open standard to build on.
Is the chat descended from Sketch?
Re: Exe.dev
#47Earlier quoted context omitted.
Hello, an exe.dev person here. There are some very early docs, exe.dev/docs (which are also accessible over ssh once you ssh in). There is a lot more to come, very early days, please bear with us. I was not expecting to see it here today.
I have played with it and it's so easy get started with that now I want a quick-project idea as an excuse to use it! I'm sure you've thought of this, but: lots of people have some amount of 'free' (or really: zero incremental cost to users) access to some coding chat tool through a subscription or free allowance like Google's. If you wanted to let those programs access your custom tools (browser!) and docs about the…
Thanks! We are thinking a lot about how to prepopulate VMs. The first thing we are going to start with is a fast ‘clone’ command, so you can preconfigure a base VM then make as many as you like. Lots of other ideas floating around too.
Re sketch: the code is not the same but the agent is deeply inspired by it. Eg the screenshot support, which just seems obvious to us. Philip has done the heavy lifting here, he hangs out in the discord if you want to chat about it.
Re: Exe.dev
#48Are there any fundamental differences between E2B and this?
Hello, exe.dev person here. I have not used E2B (though I really like their web site), though it looks like there are quite a few differences. Our disks are persistent (without manual snapshotting), we have a TLS proxy by default with built-in auth and link sharing. It also looks like they have many features we do not have (yet). I believe the target use is also quite different. You can use exe.dev VMs for running yo…
Thanks for the response. In the "How exe works" page, it's mentioned that exe runs on bare metal with Kata containers, how is it different from firecracker? Were there any advantages?
Re: Exe.dev
#49Earlier quoted context omitted.
Apologies for the vagueness of the home page, we were not expecting to be here today. There is a little more info in our first blog post https://blog.exe.dev/meet-exe.dev and docs, but far needs to be written. (We have also built some interesting tech behind this that we are excited to write up, I have a doc two pages long of blog posts we want to write.)
The blog doesn't work on Firefox on Android for me https://blog.exe.dev/meet-exe.dev Secure Connection Failed The page you are trying to view cannot be shown because the authenticity of the received data could not be verified. Please contact the website owners to inform them of this problem.
Works fine on Firefox/Android here
Re: Exe.dev
#50Some actual details here: https://exe.dev/docs/how-exedev-works https://exe.dev/docs/pricing
this post is downvoted, but these links are the meat everyone is complaining about missing
Please don't comment about downvotes. This is in the site guidelines: https://news.ycombinator.com/newsguidelines.html.
If the downvotes were inappropriate, other users will usually correct them. In this case the comment ended up being heavily upvoted.
Unfortunately, complaints like the one you added don't get garbage-collected when that happens, so they linger on, adding noise to the thread.