public/headscale
1
0
Fork 0
mirror of https://github.com/juanfont/headscale.git synced 2026-02-21 12:10:30 +09:00
Code Issues Actions 7 Packages Projects Releases Wiki Activity

Fix minor formatting issue in FAQ
Some checks failed
Deploy docs / deploy (push) Waiting to run
Details
Build / build-nix (push) Has been cancelled
Details
Build / build-cross (GOARCH=amd64 GOOS=darwin) (push) Has been cancelled
Details
Build / build-cross (GOARCH=amd64 GOOS=linux) (push) Has been cancelled
Details
Build / build-cross (GOARCH=arm64 GOOS=darwin) (push) Has been cancelled
Details
Build / build-cross (GOARCH=arm64 GOOS=linux) (push) Has been cancelled
Details
Check Generated Files / check-generated (push) Has been cancelled
Details
NixOS Module Tests / nix-module-check (push) Has been cancelled
Details
Tests / test (push) Has been cancelled
Details

Browse Source 
This just fixes a small issue I noticed reading the docs: the two 'scenarios' listed in the scaling section end up showing up as a numbered list of five items, instead of the desired two items + their descriptions.
This commit is contained in:
Brandon Sprague
2026-02-20 06:36:14 -08:00
committed by nblock
parent 13ebea192c
commit a0d6802d5b
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/about/faq.md
View File

@@ -73,12 +73,12 @@ of Headscale:
1. An environment with 1000 servers 1. An environment with 1000 servers
- they rarely "move" (change their endpoints) - they rarely "move" (change their endpoints)
- new nodes are added rarely - new nodes are added rarely
2. An environment with 80 laptops/phones (end user devices) 2. An environment with 80 laptops/phones (end user devices)
- nodes move often, e.g. switching from home to office - nodes move often, e.g. switching from home to office
Headscale calculates a map of all nodes that need to talk to each other, Headscale calculates a map of all nodes that need to talk to each other,
creating this "world map" requires a lot of CPU time. When an event that creating this "world map" requires a lot of CPU time. When an event that