Go to file
2024-10-24 19:52:08 +02:00
AppDir Embed default daemon.yml directly in entrypoint 2024-09-24 11:27:54 +02:00
dist/linux Embed default daemon.yml directly in entrypoint 2024-09-24 11:27:54 +02:00
docs Update documentation 2024-10-03 18:59:48 +02:00
go Implement SetConfig, but in a stupid way 2024-10-24 19:52:08 +02:00
nix Embed default daemon.yml directly in entrypoint 2024-09-24 11:27:54 +02:00
tests Support configuring more than one network 2024-09-10 22:51:33 +02:00
.gitignore Adjust .gitignore after change to yml 2022-11-05 16:32:26 +01:00
default.nix Remove bootstrap argument from default.nix 2024-10-15 21:45:29 +02:00
flake.lock Make sure we can use nix cache for non-cross-compiling 2023-03-25 17:05:29 +01:00
flake.nix Perform all in-code renames which don't affect actual functionality 2023-08-05 23:53:17 +02:00
LICENSE.txt Add AGPLv3 license 2023-08-25 14:16:52 +02:00
README.md Update documentation 2024-10-03 18:59:48 +02:00
release.nix Fix arch package cross-compiling 2024-07-14 15:26:34 +02:00
release.sh Fixes for releasing 2024-07-14 13:56:43 +02:00
shell.nix Add ./go/tests.sh 2024-10-05 21:12:29 +02:00
tests.sh Add tests for DNS 2023-09-06 21:55:05 +02:00

This project is currently in early-access deep-alpha testing phase. Do not rely on it for anything.


Isle

Welcome to Isle's technical documentation. You can find a less technical entrypoint to Isle on the Micropelago website.

Isle runs on a host as a server daemon, and connects to other isle instances to form a peer-to-peer network. Isle networks are completely self-hosted; no third-parties are required for a network to function.

Members of a network are able to build upon the capabilities provided by Isle to host services for themselves and others. These capabilities include:

  • A VPN which enables direct peer-to-peer communication between network members. Even if most hosts in the network are on a private LAN (e.g. their home WiFi network) or have a dynamic IP, they can still communicate directly with each other.

  • An S3-compatible network filesystem. Each member can provide as much storage as they care to, if any. Stored data is sharded and replicated across all hosts that choose to provide storage.

  • A DNS server which provides automatic host discovery within the network.

Every isle daemon is able to create or join multiple independent networks. In this case the networks remain siloed from each other, such that members of one network are unable to access resources or communicate with members of the other.

Getting Started

The following pages will guide you through setup of Isle, joining an existing network, and all other functionality available via the command-line.

Those who want to dive in and contribute to the Isle codebase should check out the Developer Documentation.