messh

But you cannot suspend these vps so easily and fast. Shellbox.dev aims to be frictionless in that regard

Currently the price is in the same ballpark as dev.exe ($20/month no suspendind) ans sprites.dev (higher for suspended butnlowe for running)

You are missing an ssh key. Run this first:

ssh-keygen -t ed25519

Simpler, easy to use, more enjoyable and fun are also valid reasons

Hetzner auction servers, not cloud

I have read about it, but currently using vanilla Firecracker w/o any memory optimizations. It is as simple as it gets for now

The feature can be discussed here: https://github.com/skariel/shellbox.issues/issues/3

This is a feature I want to implement: an option to keep boxes running while disconnected. Maybe with something like

ssh shellbox.dev keepalive box1

If it is successful then the next region would be in the US

I was born in Argentina, so technically American, yes ;)

WIP, this is still in MVP phase...

Hi thanks for the interest!

This is all written in python and the AsyncSSH package. Firecracker for VMs with memory mapped files for ram. Paddle for billing. Caddy as a reverse proxy for certificates.

It works on top of very large bare metal instances.

I'm thinking maybe open sourcing but it will take some more work on the code to make it publishable w/o embarrassing myself :)

One difference other than price is that sprites doesn't seem to use ssh

I think exe.dev is subscription. In Shellbox.dev you have funds and pay very little when not connected

Maybe you mean keypub.sh? That is another project of mine with similar graphic design.

Hi, That is a good point actually. The suspended price has to be significantly lower than the alternative. I'll revise it.

Still, there is the advantage of simplicity not having to deal with the web console etc. Some people may enjoy this

checkout also https://shellbox.dev/ which has pure ssh access

see also https://shellbox.dev/ which addresses similar problems. I like it better as it uses pure ssh

in the middle there is pair programming with ai, see for e.g. aider: https://aider.chat/

I agree there is an issue here -- btw, you would notice when eventually the server key changes.

User friendly and secure-by-default clients will leverage the domain HTTPS CA to solve this (fetching the server key using https). The downside is that it will require d/l and install

Best practice:

Use SSH keys for SSH connections and authentication

Use PGP keys for email encryption and file signing

Keep these systems separate as they're designed for different purposes

a "server-rendered" CLI is exactly what `keypub.sh` is, and what many ssh apps are (some are more TUI)

there is email validation, and the public key is handled between the ssh client and server. If there is no valid public key this code would not even run. The fingerprint is prepared from this valid public key.

Regarding having the email in the ssh pub key: maybe it is there, but it is no validated. Anyone could write anything there

will add them both. Initially I looked at "about" and "why" as suitable only for the landing page

github public ssh keys are not connected to mails. and using the api from the terminal requires installing some tool.

I hope there will be lots of apps for the the terminal, for e.g. cde (cloud dev env) managing, task management, project management, compute as a service, etc.

it does have authorization with the `allow` and `deny` commands for granular control of who can can see what. Currently very simple, only for email but maybe other fields in the future

hi, good catch of the binary! (will fix)

`Wish` and also `terminal.shop` were both great sources of inspiration. I hope to see many more ssh apps in the future. I'm already working on the next one