ctmesh/web
2
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

fixes
All checks were successful
Deploy Pages / deploy (push) Successful in 21s
Details

Browse Source
This commit is contained in:
Noah
2026-02-10 15:46:37 -05:00
parent 027b481290
commit 627c970374
3 changed files with 16 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
meshtastic-resources.html
View File

@ -132,6 +132,14 @@
.community-tools li {
margin-bottom: 0.5em;
}
.note {
background: #F5F5F5;
border-left: 4px solid #2B3A4E;
border-radius: 8px;
padding: 0.75em 1em;
margin: 0.75em 0 0.5em;
font-size: 0.95em;
}
.page-header {
display: flex;
align-items: center;
@ -175,7 +183,8 @@
opacity: 0.4;
}
.btn[target="_blank"]::after,
.copy-btn::after {
.copy-btn::after,
.site-footer a::after {
display: none;
}
.site-footer {
@ -251,7 +260,6 @@
<h3>Key Settings</h3>
<div class="code-block">
<button class="copy-btn" type="button" data-copy-target="meshtastic-mqtt">Copy all</button>
<pre id="meshtastic-mqtt">MQTT > Enabled > ON
MQTT > Encryption Enabled > ON
MQTT > Map Report > OFF
@ -267,8 +275,7 @@ Channels > Primary Channel > MQTT Downlink > OFF
Settings > Modules > Neighbor Info > ON
LoRa > Ok to MQTT > ON</pre>
</div>
<p><strong>Note:</strong> CT Mesh's MQTT server is bridged and uplinks to the MQTT servers for both <a href="https://meshtastic.liamcottle.net" target="_blank">meshtastic.liamcottle.net</a> and <a href="https://meshmap.net" target="_blank">meshmap.net</a>.</p>
<div class="note"><strong>Note:</strong> CT Mesh's MQTT server is bridged and uplinks to the MQTT servers for both <a href="https://meshtastic.liamcottle.net" target="_blank">meshtastic.liamcottle.net</a> and <a href="https://meshmap.net" target="_blank">meshmap.net</a></div>
<h2>Infrastructure Nodes</h2>
<p><strong>Important:</strong> Infrastructure roles like <code>ROUTER</code>, <code>REPEATER</code>, <code>ROUTER_CLIENT</code>, or <code>ROUTER_LATE</code> are rarely appropriate. Unless your node is sitting on top of one of the tallest buildings in Hartford with clear line-of-sight across the region, using these roles will hurt more than help. For almost everyone, the correct choice is <code>CLIENT</code>. If you think you've got a node that truly warrants an infrastructure role, reach out first - we'd rather make sure it benefits the mesh than inadvertently weakens it.</p>