hackclub/burrow
1
0
Fork 0
Code Pull requests Releases Packages Activity Actions

Wire Forge-native release infrastructure
Some checks failed
Cache: Publish Nix / Publish Nix Cache (push) Waiting to run
Details
Build Rust / Cargo Test (push) Successful in 4m14s
Details
Build Site / Next.js Build (push) Failing after 6s
Details
Infra: OpenTofu / OpenTofu (grafana) (push) Successful in 5s
Details
Lint Governance / BEP Metadata (push) Successful in 0s
Details
Build: Android / Android Rust Core Stub (push) Failing after 23s
Details

Browse source
This commit is contained in:
Conrad Kramer 2026-06-07 05:51:12 -07:00
parent 97c569fb35
commit 002bd382e9
199 changed files with 14268 additions and 185 deletions
Download patch file Download diff file Expand all files Collapse all files

7
docs/GTK_APP.md
View file

@ -1,7 +1,10 @@
# Linux GTK App Getting Started
Currently, the GTK App can be built as a binary or as an AppImage.
Note that the flatpak version can compile but will not run properly!
Currently, the GTK App can be built as a binary or as an AppImage. The Flatpak
lane is a GUI packaging target until Burrow has a verified host daemon/helper
path for TUN, routes, DNS, and firewall state. The intended Flatpak behavior is
to discover and talk to a native Burrow daemon installed by DEB, RPM, or the
NixOS flake/module, not to own privileged routing itself.
## Dependencies