public/headscale
1
0 Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-10-27 00:36:49 +09:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos
Build / build-nix (push) Waiting to run
Build / build-cross (GOARCH=amd64 GOOS=darwin) (push) Waiting to run
Build / build-cross (GOARCH=amd64 GOOS=linux) (push) Waiting to run
Build / build-cross (GOARCH=arm64 GOOS=darwin) (push) Waiting to run
Build / build-cross (GOARCH=arm64 GOOS=linux) (push) Waiting to run
Deploy docs / deploy (push) Waiting to run
Tests / test (push) Waiting to run

Browse Source 
Found via `codespell -L shs,hastable,userr`
This commit is contained in:
Kian-Meng Ang authored and nblock committed 2025-07-21 12:06:07 +02:00
1 parent 7fce5065c4
commit 3123d5286b
6 files changed
+13 -13
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

docs/about/faq.md
+1 -1
View File
@@ -76,7 +76,7 @@ new "world map" is created for every node in the network.
This means that under certain conditions, Headscale can likely handle 100s
of devices (maybe more), if there is _little to no change_ happening in the
network. For example, in Scenario 1, the process of computing the world map is
extremly demanding due to the size of the network, but when the map has been
extremely demanding due to the size of the network, but when the map has been
created and the nodes are not changing, the Headscale instance will likely
return to a very low resource usage until the next time there is an event
requiring the new map.