Tailscale on Producthunt daily

webvm

Tue, 15 Jul 2025 15:33:14 +0800

leaningtech/webvm

WebVM

This repository hosts the source code for https://webvm.io, a Linux virtual machine that runs in your browser.

Try out the new Alpine / Xorg / i3 graphical environment: https://webvm.io/alpine.html

WebVM is a server-less virtual environment running fully client-side in HTML5/WebAssembly. It’s designed to be Linux ABI-compatible. It runs an unmodified Debian distribution including many native development toolchains.

WebVM is powered by the CheerpX virtualization engine, and enables safe, sandboxed client-side execution of x86 binaries on any browser. CheerpX includes an x86-to-WebAssembly JIT compiler, a virtual block-based file system, and a Linux syscall emulator.

Enable networking

Modern browsers do not provide APIs to directly use TCP or UDP. WebVM provides networking support by integrating with Tailscale, a VPN network that supports WebSockets as a transport layer.

Open the “Networking” panel from the side-bar
Click “Connect to Tailscale” from the panel
Log in to Tailscale (create an account if you don’t have one)
Click “Connect” when prompted by Tailscale
If you are unfamiliar with Tailscale or would like additional information see WebVM and Tailscale.

Fork, deploy, customize

Fork the repository.
Enable Github pages in settings.
- Click on Settings.
- Go to the Pages section.
- Select Github Actions as the source.
  - If you are using a custom domain, ensure Enforce HTTPS is enabled.
Run the workflow.
- Click on Actions.
- Accept the prompt. This is required only once to enable Actions for your fork.
- Click on the workflow named Deploy.
- Click Run workflow and then once more Run workflow in the menu.
After a few seconds a new Deploy workflow will start, click on it to see details.
After the workflow completes, which takes a few minutes, it will show the URL below the deploy_to_github_pages job.

You can now customize dockerfiles/debian_mini to suit your needs, or make a new Dockerfile from scratch. Use the Path to Dockerfile workflow parameter to select it.

Run WebVM locally with a custom Debian mini disk image

Clone the WebVM Repository

1
2

git clone https://github.com/leaningtech/webvm.git
cd webvm

Download the Debian mini Ext2 image

Run the following command to download the Debian mini Ext2 image:
1

wget "https://github.com/leaningtech/webvm/releases/download/ext2_image/debian_mini_20230519_5022088024.ext2"
(You can also build your own disk image by selecting the “Upload GitHub release” workflow option)
Update the configuration file

Edit config_public_terminal.js to reference your local disk image:

Replace:

"wss://disks.webvm.io/debian_large_20230522_5044875331.ext2"

With:

"/disk-images/debian_mini_20230519_5022088024.ext2"

(Use an absolute or relative URL pointing to the disk image location.)
Replace "cloud" with the correct disk image type: "bytes"

Build WebVM

Run the following commands to install dependencies and build WebVM:
1 2

npm install npm run build
The output will be placed in the build directory.
Configure Nginx

Create a directory for the disk image:

1
2

mkdir disk-images
mv debian_mini_20230519_5022088024.ext2 disk-images/

Modify your nginx.conf file to serve the disk image. Add the following location block:

location /disk-images/ {
    root .;
    autoindex on;
}

Start Nginx

Run the following command to start Nginx:
1

nginx -p . -c nginx.conf
Nginx will automatically serve the build directory.
Access WebVM

Open a browser and visit: http://127.0.0.1:8081.

Enjoy your local WebVM!

Example customization: Python3 REPL

The Deploy workflow takes into account the CMD specified in the Dockerfile. To build a REPL you can simply apply this patch and deploy.

diff --git a/dockerfiles/debian_mini b/dockerfiles/debian_mini
index 2878332..1f3103a 100644
--- a/dockerfiles/debian_mini
+++ b/dockerfiles/debian_mini
@@ -15,4 +15,4 @@ WORKDIR /home/user/
 # We set env, as this gets extracted by Webvm. This is optional.
 ENV HOME="/home/user" TERM="xterm" USER="user" SHELL="/bin/bash" EDITOR="vim" LANG="en_US.UTF-8" LC_ALL="C"
 RUN echo 'root:password' | chpasswd
-CMD [ "/bin/bash" ]
+CMD [ "/usr/bin/python3" ]

How to use Claude AI

To access Claude AI, you need an API key. Follow these steps to get started:

Create an account

Visit Anthropic Console and sign up with your e-mail. You’ll receive a sign in link to the Anthropic Console.

Get your API key

Once logged in, navigate to Get API keys.
Purchase the amount of credits you need. After completing the purchase, you’ll be able to generate the key through the API console.

Navigate to your WebVM and hover over the robot icon. This will show the Claude AI Integration tab. For added convenience, you can click the pin button in the top right corner to keep the tab in place.
You’ll see a prompt where you can insert your Claude API key.
Insert your key and press enter.

Start using Claude AI

Once your API key is entered, you can begin interacting with Claude AI by asking questions such as:

“Solve the CTF challenge at /home/user/chall1.bin. Note that the binary reads from stdin.”

Important: Your API key is private and should never be shared. We do not have access to your key, which is not only stored locally in your browser.

Bugs and Issues

Please use Issues to report any bug. Or come to say hello / share your feedback on Discord.

Thanks to…

This project depends on:

CheerpX, made by Leaning Technologies for x86 virtualization and Linux emulation
xterm.js, https://xtermjs.org/, for providing the Web-based terminal emulator
Tailscale, for the networking component
lwIP, for the TCP/IP stack, compiled for the Web via Cheerp

Versioning

WebVM depends on the CheerpX x86-to-WebAssembly virtualization technology, which is included in the project via NPM.

The NPM package is updated on every release.

Every build is immutable, if a specific version works well for you today, it will keep working forever.

License

WebVM is released under the Apache License, Version 2.0.

You are welcome to use, modify, and redistribute the contents of this repository.

The public CheerpX deployment is provided as-is and is free to use for technological exploration, testing and use by individuals. Any other use by organizations, including non-profit, academia and the public sector, requires a license. Downloading a CheerpX build for the purpose of hosting it elsewhere is not permitted without a commercial license.

headscale

Tue, 06 May 2025 15:29:52 +0800

juanfont/headscale

An open source, self-hosted implementation of the Tailscale control server.

Join our Discord server for a chat.

Note: Always select the same GitHub tag as the released version you use to ensure you have the correct example configuration. The main branch might contain unreleased changes. The documentation is available for stable and development versions:

What is Tailscale

Tailscale is a modern VPN built on top of Wireguard. It works like an overlay network between the computers of your networks - using NAT traversal.

Everything in Tailscale is Open Source, except the GUI clients for proprietary OS (Windows and macOS/iOS), and the control server.

The control server works as an exchange point of Wireguard public keys for the nodes in the Tailscale network. It assigns the IP addresses of the clients, creates the boundaries between each user, enables sharing machines between users, and exposes the advertised routes of your nodes.

A Tailscale network (tailnet) is private network which Tailscale assigns to a user in terms of private users or an organisation.

Design goal

Headscale aims to implement a self-hosted, open source alternative to the Tailscale control server. Headscale’s goal is to provide self-hosters and hobbyists with an open-source server they can use for their projects and labs. It implements a narrow scope, a single Tailscale network (tailnet), suitable for a personal use, or a small open-source organisation.

Supporting Headscale

If you like headscale and find it useful, there is a sponsorship and donation buttons available in the repo.

Features

Please see “Features” in the documentation.

Client OS support

Please see “Client and operating system support” in the documentation.

Running headscale

Please note that we do not support nor encourage the use of reverse proxies and container to run Headscale.

Please have a look at the documentation.

Talks

Fosdem 2023 (video): Headscale: How we are using integration testing to reimplement Tailscale
- presented by Juan Font Alonso and Kristoffer Dalby

Disclaimer

This project is not associated with Tailscale Inc.

However, one of the active maintainers for Headscale is employed by Tailscale and he is allowed to spend work hours contributing to the project. Contributions from this maintainer are reviewed by other maintainers.

The maintainers work together on setting the direction for the project. The underlying principle is to serve the community of self-hosters, enthusiasts and hobbyists - while having a sustainable project.

Contributing

Please read the CONTRIBUTING.md file.

Requirements

To contribute to headscale you would need the latest version of Go and Buf (Protobuf generator).

We recommend using Nix to setup a development environment. This can be done with nix develop, which will install the tools and give you a shell. This guarantees that you will have the same dev env as headscale maintainers.

Code style

To ensure we have some consistency with a growing number of contributions, this project has adopted linting and style/formatting rules:

The Go code is linted with golangci-lint and formatted with golines (width 88) and gofumpt. Please configure your editor to run the tools while developing and make sure to run make lint and make fmt before committing any code.

The Proto code is linted with buf and formatted with clang-format.

The rest (Markdown, YAML, etc) is formatted with prettier.

Check out the .golangci.yaml and Makefile to see the specific configuration.

Install development tools

Go
Buf
Protobuf tools

Install and activate:

`1`	`nix develop`

Testing and building

Some parts of the project require the generation of Go code from Protobuf (if changes are made in proto/) and it must be (re-)generated with:

`1`	`make generate`

Note: Please check in changes from gen/ in a separate commit to make it easier to review.

To run the tests:

`1`	`make test`

To build the program:

`1`	`nix build`

`1`	`make build`

Contributors

Made with contrib.rocks.