[pomdtr]

Yeah dokku is an inspiration!

The main difference is that smallweb use deno instead of docker for sandboxing apps, and leverages url imports (which can be used to distribute complex apps like VS Code):

```

import { VSCode } from "jsr:@smallweb/vscode@0.1.7"

const vscode = new VSCode({ rootDir: Deno.env.get("SMALLWEB_DIR") });

export default vscode;

```

You can play with a live instance of smallweb at https://demo.smallweb.live

[yencabulator]

By "VSCode" here you mean something like a HTTP API for file read/write[0] that can be used from VSCode, I think? VSCode also can be made into a web app[1], but I don't see that happening here.

[0]: https://github.com/pomdtr/smallweb-vscode/blob/main/extensio...

[1]: https://github.com/gitpod-io/openvscode-server https://github.com/coder/code-server etc

[pomdtr]

By vscode I mean vscode-web + an fsprovider extension.

You can play with it at https://vscode.demo.smallweb.live (the code is located in the `vscode` folder)

[diggan]

> The main difference is that smallweb use deno instead of docker for sandboxing apps

Yeah, a single-runtime (smallweb) instead of any language (dokku) + I'd probably say the avoidance of using git for the delivery would be the two biggest differences I can glance.

[pomdtr]

Yeah, I see smallweb as a playground.

I want to "develop in prod", not rely on successives git pushes to see changes.

If I need semantic releases, I publish the dev version as a package on jsr, and I then import it from the "prod" app.

I still uses github as way to store my apps though, you can find them at https://github.smallweb.run