From 7870f132c2fcc13eab32eba0a912583ad5560a72 Mon Sep 17 00:00:00 2001
From: phm07 <22707808+phm07@users.noreply.github.com>
Date: Thu, 23 May 2024 13:30:17 +0200
Subject: [PATCH] update documentation

---
 README.md | 37 +++++++++++++++++++++++++------------
 1 file changed, 25 insertions(+), 12 deletions(-)

diff --git a/README.md b/README.md
index 06174ba6..809025a5 100644
--- a/README.md
+++ b/README.md
@@ -142,18 +142,31 @@ You can control output via the `-o` option:
   The template’s input is the resource’s corresponding struct in the
   [hcloud-go](https://godoc.org/github.com/hetznercloud/hcloud-go/hcloud) library.
 
-## Configure hcloud using environment variables
-
-You can use the following environment variables to configure `hcloud`:
-
-* `HCLOUD_TOKEN`
-* `HCLOUD_CONTEXT`
-* `HCLOUD_CONFIG`
-
-When using `hcloud` in scripts, for example, it may be cumbersome to work with
-contexts. Instead of creating a context, you can set the token via the `HCLOUD_TOKEN`
-environment variable. When combined with tools like [direnv](https://direnv.net), you
-can configure a per-directory context by setting `HCLOUD_CONTEXT=my-context` via `.envrc`.
+## Configuring hcloud
+
+The hcloud CLI tool allows configuration using following methods:
+1. Configuration file
+2. Environment variables
+3. Command line flags
+
+A higher number means a higher priority. For example, a command line flag will 
+always override an environment variable.
+
+The configuration file is located at `~/.config/hcloud/cli.toml` by default 
+(On Windows: `%APPDATA%\hcloud\cli.toml`). You can change the location by setting 
+the `HCLOUD_CONFIG` environment variable or the `--config` flag. The configuration file
+stores global preferences, the currently active context, all contexts and 
+context-specific preferences. Contexts always store a token and can optionally have
+additional preferences which take precedence over the globally set preferences.
+
+However, a config file is not required. If no config file is found, the CLI will
+use the default configuration. Overriding options using environment variables allows 
+hcloud CLI to function in a stateless way. For example, setting `HCLOUD_TOKEN` is
+already enough in many cases.
+
+You can use the `hcloud config` command to manage your configuration, for example 
+to get, list, set and unset configuration options and preferences. You can view a list
+of all available options and preferences by running `hcloud config --help`.
 
 ## Examples