From 9f910b2c1eefee358b017ed6f0cb1685436e4769 Mon Sep 17 00:00:00 2001 From: Noah Date: Tue, 10 Feb 2026 19:10:54 -0500 Subject: [PATCH 1/2] fix deploy workflow for main branch --- .gitea/workflows/deploy.yml | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/.gitea/workflows/deploy.yml b/.gitea/workflows/deploy.yml index 9ec5672..36ce362 100644 --- a/.gitea/workflows/deploy.yml +++ b/.gitea/workflows/deploy.yml @@ -12,9 +12,16 @@ jobs: - uses: actions/checkout@v4 - run: mkdir /tmp/deploy - run: rsync -ua --exclude=".*" . /tmp/deploy + - name: Set deploy branch + run: | + if [ "${{ github.ref_name }}" = "master" ]; then + echo "DEPLOY_BRANCH=main" >> "$GITHUB_ENV" + else + echo "DEPLOY_BRANCH=${{ github.ref_name }}" >> "$GITHUB_ENV" + fi - name: Build & Deploy Worker uses: cloudflare/wrangler-action@v3 with: apiToken: ${{ secrets.CF_API_TOKEN }} accountId: ${{ secrets.CF_ACCOUNT_ID }} - command: pages deploy /tmp/deploy --project-name=ctmesh-org --branch=${{ github.ref_name }} + command: pages deploy /tmp/deploy --project-name=ctmesh-org --branch=${{ env.DEPLOY_BRANCH }} From 04a1af17cd3963887f3db2c4f97ac6e750754fb9 Mon Sep 17 00:00:00 2001 From: Jared Dunbar Date: Mon, 2 Mar 2026 22:33:17 -0500 Subject: [PATCH 2/2] Improve outreach information --- index.html | 14 ++- why-run-a-node.html | 294 ++++++++++++++++++++++++++++++++++++++++++++ 2 files changed, 307 insertions(+), 1 deletion(-) create mode 100644 why-run-a-node.html diff --git a/index.html b/index.html index 6a87c92..084a294 100644 --- a/index.html +++ b/index.html @@ -165,6 +165,11 @@ background-color: #2B3A4E; color: #ffffff; } + .btn-learn, + .btn-learn:visited { + background-color: #FFB347; + color: #1F2230; + } .btn-meshcore img { filter: brightness(0) invert(1); } @@ -319,13 +324,20 @@
- + Discord
Join our Discord Chat with the community
+ + Learn about mesh networking +
+ Why Mesh Matters + Learn about the mesh! +
+
diff --git a/why-run-a-node.html b/why-run-a-node.html new file mode 100644 index 0000000..db37dd2 --- /dev/null +++ b/why-run-a-node.html @@ -0,0 +1,294 @@ + + + + + + Why Run a Mesh Node? | CT Mesh + + + + + + + + + +
+
+ + CT Mesh + CT Mesh + + +

Why Run a Mesh Node?

+

Learn about the mesh!

+

A local node is more than a gadget. It strengthens community communication by adding coverage, redundancy, and local routing for everyone nearby.

+ +

How the Public Benefits

+
    +
  • Resilient network without internet or cellular dependency: Nodes route locally by radio and create alternate paths, so communication can continue even when phone or ISP backbones are unavailable.
    • +
  • Emergency communication: During outages or disasters, local radio links can keep basic coordination available.
    • +
  • Flexible encrypted communications: Mesh platforms support public channels for open community traffic, private encrypted channels for groups, and private encrypted direct messages between individuals.
    • +
  • Accessible mobile apps: Both iPhone and Android users can manage nodes and messaging from their phones, using Bluetooth to communicate with the radios.
    • +
  • Affordable hardware: Many compatible devices are commonly available for under $100.
    • +
  • No operator license required (USA): On 915 MHz ISM, operation under 1W does not require an amateur radio license, and this is typically plenty of power for local mesh use.
    • +
  • Easy onboarding: Pairing a node, loading channels, and joining local community resources is straightforward for new users.
    • +
+ +

Solar and Off-Grid Operation

+

Many fixed mesh repeater nodes can run from small solar systems and batteries, with no grid connection required. That means:

+
    +
  • Improved resilience because communication infrastructure can remain active during grid disruptions
    • +
  • Install options beyond existing infrastructure, including remote locations with clear line-of-sight and reliable sun exposure
    • +
  • No additional household electric cost for grid power at the node site
    • +
+ +

Why Ham Radio Operators Often Love Mesh

+
    +
  • It combines RF experimentation, antenna work, and practical local service.
    • +
  • It rewards good station design: Elevation, feedline quality, power planning, and interference control.
    • +
  • It offers an always-on local network that can complement other emergency and community communication practices.
    • +
  • These communities represent some of the largest mesh networks in the world: Over 21,000 MeshCore nodes globally (including about 14,000 repeaters) and over 32,000 Meshtastic nodes worldwide, with adoption levels comparable to APRS and major amateur IP mesh networks in Europe.
    • +
+

Getting Involved

+

Most users only need a companion/client device. If you want to expand mesh coverage in your area, build a repeater/router node. In MeshCore, a repeater is a fixed station that stays in place to relay traffic for the mesh, while a companion is a personal device that travels with you for day-to-day messaging. Meshtastic follows a similar pattern with routers (fixed relay-focused nodes) and clients (user-focused mobile/personal nodes). Contact us on Discord if you want help building or operating a repeater.

+ +

Recommended Hardware

+
    +
  • Heltec LoRa 32 V4 - popular low-cost option and a common first node. Typical price: $25-$35.
    • +
  • LILYGO T-Echo - portable handheld form factor with an integrated display and battery support. Typical price: $40-$80 depending on configuration.
    • +
  • RAK4631 Development Board - a common choice for reliable fixed installations with low-power operation and flexible deployment options. Typical combined core + base price: $30-$45.
    • +
+ +

Typical Installation Locations

+

Fixed nodes in strong locations often improve neighborhood coverage for many nearby users, not just the node owner, and even modest elevation can make a big difference. For example, an upstairs attic-window repeater can significantly improve in-home and neighborhood reception, and a few extra feet of height can meaningfully improve overall mesh performance.

+
    +
  • Indoor locations: Attic or top-floor window positions with clear line-of-sight.
    • +
  • Outdoor home locations: Rooftop mast or chimney mount, balcony rail, garage or shed roof, fences, trees, and old over-the-air TV antenna roof mounts.
    • +
  • Hosted or remote sites: Hilltop, tower, or shared hosted locations with sun exposure for solar operation, including off-grid sites with no utility infrastructure.
    • +
  • Mobile deployments: Vehicle-based nodes for mapping and temporary event coverage.
    • +
+
Safety Note: Use a spotter when working on a ladder or on a roof.
+ +

Meshtastic vs MeshCore in CT Mesh

+

Both platforms are still useful, and many members experiment with both. In the CT Mesh fixed-node community, Meshtastic has gradually been replaced in many deployments by MeshCore as operators have seen stronger day-to-day reliability and broader platform functionality from current MeshCore firmware.

+

If you are starting fresh and your goal is reliable fixed-node service, MeshCore is often the first recommendation from local operators.

+ +

Learn More

+

Start with our local guides, then review official project docs and community channels to choose the right platform for your goals.

+
+ MeshCore Guides & Tools + Meshtastic Guides & Tools + Join CT Mesh Discord + Official MeshCore Site + Official Meshtastic Site +
+ + Back to CT Mesh + + +
+ +