gem-hunter
Language: Go
A CLI to create code sandboxes with automatic HTTPS and long running processes in your cloud provider account
Code sandboxes with automatic HTTPS and long running processes. Running in VMs in your cloud provider account.
Currently available on Amazon Web Services and Hetzner.
... use it as a remote development environment, to test some code or even to deploy your app. It's up to you!
eleven aws init hello-world --runtimes node@18.7.0 --repositories eleven-sh/hello-world
... now that this sandbox is created, you can connect to it with your preferred editor:
eleven aws edit hello-world
... finally, now that you have finished working on your application, you may want to deploy it:
me@home:~$ ssh eleven/hello-world # or use your editor's integrated terminal
eleven@hello-world:~/workspace/hello-world$ node index.js # test that your app starts (optional) Server running at http://127.0.0.1:8000/ ^C (Control-C) eleven@hello-world:~/workspace/hello-world$ forever node index.js Forever: command started. Run "forever stop" in current path to stop. eleven@hello-world:~/workspace/hello-world$ exit Connection to 34.202.238.110 closed.
... add an A record pointing to your sandbox's public IP address for the domain that you want to use, then run:
me@home:~$ eleven aws serve hello-world 8000 --as hello.eleven.sh Success! The port "8000" is now reachable at: https://hello.eleven.sh me@home:~$ curl https://hello.eleven.sh Hello World
The Eleven CLI has been tested on Linux and MacOS. Support for Windows is theoretical (testers needed 💙).
Before using Eleven, the following dependencies need to be installed:
Before running the edit command, one of the following editors need to be installed:
The process required to install the Eleven CLI vary depending on your operating system:
On Linux and MacOS, the easiest way to install it is by running the following command in your terminal:
curl -sf https://raw.githubusercontent.com/eleven-sh/cli/main/install.sh | sh -s -- -b /usr/local/bin latestThis command could be run as-is or by changing:
The installation directory by replacing /usr/local/bin with your preferred path.
The version installed by replacing latest with a specific version.
On Windows, the easiest way is by running the following Powershell script:
irm https://raw.githubusercontent.com/eleven-sh/cli/main/install.ps1 | iexOnce done, you could confirm that Eleven is installed by running the eleven command:
eleven --help
The command used to install Eleven could also be used to update it to another version.
To begin, run the command "eleven login" to connect your GitHub account. From there, the most common workflow is: - eleven <cloud_provider> init <sandbox_name> : to initialize a new sandbox - eleven <cloud_provider> edit <sandbox_name> : to connect your preferred editor to a sandbox - eleven <cloud_provider> remove <sandbox_name> : to remove an existing sandbox Usage: eleven [command] Available Commands: aws Use Eleven on Amazon Web Services completion Generate the autocompletion script for the specified shell help Help about any command hetzner Use Eleven on Hetzner login Connect a GitHub account Flags: -h, --help help for eleven -v, --version version for eleven Use "eleven [command] --help" for more information about a command.
eleven login
To begin, you need to run the login command to connect your GitHub account.
Eleven requires the following permissions:
"Public SSH keys" and "Repositories" to let you access your repositories from your sandboxes.
"Personal user data" to configure Git.
All your data (including the OAuth access token) are only stored locally in ~/.config/eleven/eleven.yml (or in XDG_CONFIG_HOME if set).
The source code that implements the GitHub OAuth flow is located in the eleven-sh/api repository.
eleven <cloud_provider> init <sandbox_name> [--instance-type=<instance_type> --runtimes=<runtimes> --repositories=<repositories>]
The init command initializes a new sandbox.
To choose the type of instance that will run the sandbox, use the --instance-type flag.
To install some runtimes in the sandbox, use the --runtimes flag.
To clone some GitHub repositories in the sandbox, use the --repositories flag.
Valid and default values for the --instance-type flag vary depending on the cloud provider used. (See the corresponding cloud provider repository to learn more).
The following runtimes could be installed in all sandboxes:
docker (latest only)
php or php@X.Y (e.g., php@8.1)
java (latest only)
node or node@X.Y.Z (e.g., node@18.7.0) (via nvm)
python or python@X.Y.Z (e.g., python@3.1.0) (via pyenv)
ruby or ruby@X.Y.Z (e.g., ruby@3.1.2) (via rvm)
rust or rust@X.Y.Z (e.g., rust@1.64.0) (via rustup)
go or go@X.Y.Z (e.g., go@1.19.0)
clang (latest only)
All runtimes will default to @latest if the version is not set.
Repositories may be fully qualified (e.g., eleven-sh/api) or without an account name (e.g., my-repo). Your personal account is assumed for repositories without an account name.
eleven aws init eleven-api
eleven aws init eleven-api --instance-type m4.large --runtimes node@18.7.0,docker --repositories repo,organization/repo
eleven <cloud_provider> edit <sandbox_name>
The edit command connects your preferred editor to a sandbox.
eleven aws edit eleven-api
eleven <cloud_provider> serve <sandbox_name> <port> [--as=<domain_name>]
The serve command allows TCP traffic on a port in a sandbox.
To reach the port through a domain name (via HTTP(S)), use the --as flag.
If you want to use more than one domain for a port, you could run the serve command multiple times with different domain names.
eleven aws serve eleven-api 8000
eleven aws serve eleven-api 8000 --as eleven.sh eleven aws serve eleven-api 8000 --as www.eleven.sh
eleven <cloud_provider> unserve <sandbox_name> <port>
The unserve command disallows TCP traffic on a port in a sandbox.
Once TCP traffic is disallowed, the port becomes unreachable from outside.
eleven aws unserve eleven-api 8000
eleven <cloud_provider> remove <sandbox_name> [--force]
The remove command removes an existing sandbox.
The sandbox will be PERMANENTLY removed along with ALL your un-pushed work.
There is no going back, so please be sure before running this command.
The --force flag could be used to remove without confirmation.
eleven aws remove eleven-api
eleven aws remove eleven-api --force
eleven <cloud_provider> uninstall
The uninstall command removes all the infrastructure components used by Eleven from your cloud provider account. (See the corresponding cloud provider repository for details).
All your sandboxes must be removed before running this command.
eleven aws uninstall
In order to ease the process of managing long running processes, a CLI named forever is available inside your sandboxes.
(Except for the name, this CLI doesn't have anything in common with the one available on npm).
forever <command>
The forever command starts the passed command in the current path and relaunches it in case of exit or after instance restart.
You cannot have more than one command running per path.
forever node index.js
forever docker compose up
forever stop
The stop command stops a command started in the current path.
In the context of Eleven, a "code sandbox" is nothing more than a VM, configured and ready-to-use, running in your cloud provider account.
It's called "code sandbox" because the code that you will run in it will be 100% isolated from your local computer (unlike containers).
The infrastructure components that will be created in your account will vary depending on the cloud provider used.
See the "Infrastructure components" section of the corresponding cloud provider repository to learn more (e.g., here for AWS and here for Hetzner).
Eleven is 100% free. However, using a VM in your cloud provider account is not.
See the "Infrastructure costs" section of the corresponding cloud provider repository to learn more (e.g., here for AWS and here for Hetzner).
Eleven is available as open source under the terms of the MIT License.