Add FAQ entry on which database to use

.prettierignore

@@ -1,3 +1,4 @@
 .github/workflows/test-integration-v2*
 docs/about/features.md
+docs/ref/configuration.md
 docs/ref/remote-cli.md

README.md

@@ -46,18 +46,18 @@ buttons available in the repo.
 
 ## Features
 
-Please see ["Features" in the documentation](https://headscale.net/about/features/).
+Please see ["Features" in the documentation](https://headscale.net/stable/about/features/).
 
 ## Client OS support
 
-Please see ["Client and operating system support" in the documentation](https://headscale.net/about/clients/).
+Please see ["Client and operating system support" in the documentation](https://headscale.net/stable/about/clients/).
 
 ## Running headscale
 
 **Please note that we do not support nor encourage the use of reverse proxies
 and container to run Headscale.**
 
-Please have a look at the [`documentation`](https://headscale.net/).
+Please have a look at the [`documentation`](https://headscale.net/stable/).
 
 ## Talks
 

docs/about/faq.md

@@ -44,6 +44,18 @@ For convenience, we also [build Docker images with headscale](../setup/install/c
 we don't officially support deploying headscale using Docker**. On our [Discord server](https://discord.gg/c84AZQhmpx)
 we have a "docker-issues" channel where you can ask for Docker-specific help to the community.
 
+## Which database should I use?
+
+We recommend the use of SQLite as database for headscale:
+
+- SQLite is simple to setup and easy to use
+- It scales well for all of headscale's usecases
+- Development and testing happens primarily on SQLite
+- PostgreSQL is still supported, but is considered to be in "maintenance mode"
+
+The headscale project itself does not provide a tool to migrate from PostgreSQL to SQLite. Please have a look at [the
+related tools documentation](../ref/integration/tools.md) for migration tooling provided by the community.
+
 ## Why is my reverse proxy not working with headscale?
 
 We don't know. We don't use reverse proxies with headscale ourselves, so we don't have any experience with them. We have

docs/ref/configuration.md

@@ -2,9 +2,9 @@
 
 - Headscale loads its configuration from a YAML file
 - It searches for `config.yaml` in the following paths:
-  - `/etc/headscale`
-  - `$HOME/.headscale`
-  - the current working directory
+    - `/etc/headscale`
+    - `$HOME/.headscale`
+    - the current working directory
 - Use the command line flag `-c`, `--config` to load the configuration from a different path
 - Validate the configuration file with: `headscale configtest`
 

docs/ref/integration/tools.md

@@ -7,6 +7,7 @@
 
 This page collects third-party tools and scripts related to headscale.
 
-| Name              | Repository Link                                                 | Description                                       |
-| ----------------- | --------------------------------------------------------------- | ------------------------------------------------- |
-| tailscale-manager | [Github](https://github.com/singlestore-labs/tailscale-manager) | Dynamically manage Tailscale route advertisements |
+| Name                  | Repository Link                                                 | Description                                       |
+| --------------------- | --------------------------------------------------------------- | ------------------------------------------------- |
+| tailscale-manager     | [Github](https://github.com/singlestore-labs/tailscale-manager) | Dynamically manage Tailscale route advertisements |
+| headscalebacktosqlite | [Github](https://github.com/bigbozza/headscalebacktosqlite)     | Migrate headscale from PostgreSQL back to SQLite  |