19 Commits

Author	SHA1	Message	Date
Brandon Sprague	a0d6802d5b	Fix minor formatting issue in FAQ ... 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.	2026-02-20 16:59:14 +01:00
Florian Preinstorfer	cfb308b4a7	Add FAQ entry to migrate back to default IP prefixes	2026-02-19 17:16:40 +01:00
Florian Preinstorfer	4bb0241257	Require to update from one version to the next	2026-02-19 17:16:40 +01:00
Florian Preinstorfer	8f60b819ec	Refresh update path	2026-02-16 15:22:46 +01:00
Florian Preinstorfer	c29bcd2eaf	Release planning happens in milestones	2026-02-16 15:22:46 +01:00
Florian Preinstorfer	249630bed8	Add API documentation ... Document the API endpoint and the built-in swagger docs at /swagger. The remote control docs are just a use case for gRPC - move it in the API docs and update links to it.	2025-11-13 15:22:55 +01:00
Florian Preinstorfer	047dbda136	Add FAQ on how to disable log submission ... Fixes: #2793	2025-10-19 08:24:23 +02:00
Florian Preinstorfer	bd35fcf338	Add FAQ entry about policy migration in the database	2025-09-17 16:32:29 +02:00
Florian Preinstorfer	30d12dafed	Add FAQ entry about the recommended upgrade path	2025-09-13 08:15:01 +02:00
Luke Watts	b2a18830ed	docs: fix typos	2025-07-28 10:28:49 +02:00
Kian-Meng Ang	3123d5286b	Fix typos ... Found via `codespell -L shs,hastable,userr`	2025-07-21 12:06:07 +02:00
Kristoffer Dalby	081af2674b	ci: fix golangci-lint flag for v2 compatibility (#2654)	2025-06-24 08:14:50 +02:00
Florian Preinstorfer	586a20fbff	Add a FAQ entry about two nodes seeing each other ... See: #2431 See: #2174	2025-03-14 18:48:44 +01:00
Kristoffer Dalby	818046f240	add faq section on scaling/performance (#2476) ... * add faq section on scaling/performance Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com> * Apply suggestions from code review Co-authored-by: nblock <nblock@users.noreply.github.com> --------- Signed-off-by: Kristoffer Dalby <kristoffer@tailscale.com> Co-authored-by: nblock <nblock@users.noreply.github.com>	2025-03-14 17:09:30 +00:00
nblock	fe06a00d45	Container images are also available on GHCR (#2470) ... Fixes: #2456	2025-03-11 06:54:05 +01:00
Florian Preinstorfer	8c09afe20c	Headscale implements a single tailnet ... Separate the term "tailnet" from user and be more explicit about providing a single tailnet. Also be more explicit about users. Refer to "headscale users" when mentioning commandline invocations and use the term "local users" when discussing unix accounts. Fixes: #2335	2025-02-05 11:05:03 +01:00
Florian Preinstorfer	75e74117db	Add FAQ entry on which database to use ... Fixes: #2257	2024-12-04 06:08:44 +01:00
nblock	a7874af3d0	Use discord server invite link (#2235) ... Replace channel links with links to discord invite link and remove channel list. Fixes: #1521	2024-11-16 07:06:15 +01:00
nblock	8c7d8ee34f	Restructure headscale documentation (#2163) ... * Setup mkdocs-redirects * Restructure existing documentation * Move client OS support into the documentation * Move existing Client OS support table into its own documentation page * Link from README.md to the rendered documentation * Document minimum Tailscale client version * Reuse CONTRIBUTING.md" in the documentation * Include "CONTRIBUTING.md" from the repository root * Update FAQ and index page and link to the contributing docs * Add configuration reference * Add a getting started page and explain the first steps with headscale * Use the existing "Using headscale" sections and combine them into a single getting started guide with a little bit more explanation. * Explain how to get help from the command line client. * Remove duplicated sections from existing installation guides * Document requirements and assumptions * Document packages provided by the community * Move deb install guide to official releases * Move manual install guide to official releases * Move container documentation to setup section * Move sealos documentation to cloud install page * Move OpenBSD docs to build from source * Simplify DNS documentation * Add sponsor page * Add releases page * Add features page * Add help page * Add upgrading page * Adjust mkdocs nav * Update wording Use the term headscale for the project, Headscale on the beginning of a sentence and `headscale` when refering to the CLI. * Welcome to headscale * Link to existing documentation in the FAQ * Remove the goal header and use the text as opener * Indent code block in OIDC * Make a few pages linter compatible Also update ignored files for prettier * Recommend HTTPS on port 443 Fixes: #2164 * Use hosts in acl documentation thx @efficacy38 for noticing this Ref: #1863 * Use mkdocs-macros to set headscale version once	2024-10-10 15:24:04 +02:00