Hey HN,<p>Eleven is the second project that I've built to learn Go. It lets you create a code sandbox in your cloud provider account easily.<p>What's a "code sandbox"? Just a VM, running in your cloud provider account, with some runtimes pre-installed, your repositories cloned, a way to connect to it with your preferred editor (or via SSH) and a way to serve your apps easily via HTTP (with automatic HTTPS).<p>You could use it to deploy your app, as a remote development environment or even to test some code. It's up to you.<p>For example, to deploy a Node.JS app:<p>$ eleven aws init hello-world --runtimes node@18.7.0 --repositories eleven-sh/hello-world<p>> Success! The sandbox "hello-world" was initialized.<p>$ ssh eleven/hello-world forever node index.js<p>> Forever: command started. Run "forever stop" in current path to stop.<p>$ eleven aws serve hello-world 8000 --as hello.eleven.sh<p>> Success! The port "8000" is now reachable at: <a href="https://hello.eleven.sh" rel="nofollow">https://hello.eleven.sh</a><p>$ curl <a href="https://hello.eleven.sh" rel="nofollow">https://hello.eleven.sh</a><p>> Hello World<p>Still learning Go by the way, so I'm open to any suggestions to improve.
Congratulations on your release<p>Please don't mandate the use of static AWS credentials; the aws sdk is capable of abstracting away all those gory details for you, including <i>allowing</i> someone to use those env-vars if they really want, but forcing them is a headache for an organization that uses AssumeRole (or its friends) for everything: <a href="https://github.com/eleven-sh/cli/blob/v0.0.4/internal/cloudproviders/aws/errors_presenter.go#L60">https://github.com/eleven-sh/cli/blob/v0.0.4/internal/cloudp...</a><p>I wasn't readily able to find the Route53 logic; how are those "serve --as" domains created/updated?
Running it in a VM is a huge maintenance overhead. This at first glance looks like a great PoC. You might have to eventually support kubernetes or ecs equivalent thing on each cloud provider from production readiness point of view as well as from admin perspective, the way gitpod works.