vvvomit/interzone
Watch
1
0
Fork
You've already forked interzone
 0
Code Issues Pull requests Projects Releases 50 Packages Wiki Activity Actions
50 releases 50 tags
  • v0.5.34 100ba9e05c

    v0.5.34 Stable

    vvvomit released this 2026-10-30 01:16:05 +03:30 | 39 commits to main since this release

    Set up from other servers over IPFS

    When the in-country mirrors are unreachable too, interzone can now fetch everything from other interzone servers over IPFS.

    IPFS: from interzone's swarm

    • A third Network situation on the Server step. The playbook, Ansible roles, OS and Docker packages, PyPI and every container image come from interzone's private IPFS swarm. The server only needs to reach one peer that has the files.
    • Before the deploy, interzone installs the IPFS daemon (kubo) on the server and joins the swarm. It finds the newest publish and checks its signature before using anything, then serves the publish's images to Docker as a local registry. The playbook is held at the publish's commit, so the roles match the images.
    • Share what this server downloads is asked during setup, with no answer preselected. Sharing keeps IPFS running after the deploy, listening on TCP 4001, and lets the swarm's members see that the server holds Matrix software. Without sharing, IPFS stops after each run.
    • ctrl+t and interzone check test that the publish and the swarm's entry node can be reached.
    • Offline bundles made with IPFS chosen carry the IPFS daemon for x86 and ARM servers.

    The swarm's key ships with interzone. It keeps the public IPFS network out but isn't a secret. See the wiki's Blackout mode page, section 6.

    Downloads