MyFavMirrors
/
headscale
mirror of https://github.com/juanfont/headscale.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
headscale/config.json.postgres.example

21 lines
593 B
Plaintext
Raw Normal View History

Initial commit
2020-06-21 06:32:08 -04:00
{
Added tests for the sqlite-based config
2021-05-15 08:36:13 -04:00
"server_url": "http://127.0.0.1:8000",
Initial commit
2020-06-21 06:32:08 -04:00
"listen_addr": "0.0.0.0:8000",
"private_key_path": "private.key",
If the configuration file contains relative paths (e.g. in the values for private_key_path or derp_map_path), interpret them as relative to the directory where the config.json file was read from.
2021-04-22 21:10:50 -04:00
"derp_map_path": "derp.yaml",
Add support for ephemeral nodes via a special type of pre-auth key. Add tests for that feature. Other fixes: clean up a few typos in comments. Fix a bug that caused the tests to run four times each. Be more consistent in the use of log rather than fmt to print errors and notices.
2021-05-22 20:15:29 -04:00
"ephemeral_node_inactivity_timeout": "30m",
Added tests for the sqlite-based config
2021-05-15 08:36:13 -04:00
"db_type": "postgres",
Initial commit
2020-06-21 06:32:08 -04:00
"db_host": "localhost",
"db_port": 5432,
"db_name": "headscale",
"db_user": "foo",
Add HTTPS support for the web endpoint with manually configured certificate/key files.
2021-04-23 16:54:35 -04:00
"db_pass": "bar",
Add support for automatic TLS certificates via Let's Encrypt. Add a configuration reference to the README.md file.
2021-04-23 22:54:15 -04:00
"tls_letsencrypt_hostname": "",
Add a 'tls_letsencrypt_listen' config option Currently the default (and non-configurable) Let's Encrypt listener will bind to all IPs. This isn't ideal if we want to run headscale on a specific IP only. This also allows for one to set the listener to something other than port 80. This is useful for OSs like OpenBSD which only allow root to bind the lower port ranges (and don't have `setcap`) as we can now run `headscale` as a non-privileged user while still using the baked in ACME magic. Obviously this configuration would also require a reverse proxy or firewall rule to redirect traffic. I attempted to outline that in the README change.
2021-07-23 18:12:01 -04:00
"tls_letsencrypt_listen": ":http",
Add support for automatic TLS certificates via Let's Encrypt. Add a configuration reference to the README.md file.
2021-04-23 22:54:15 -04:00
"tls_letsencrypt_cache_dir": ".cache",
"tls_letsencrypt_challenge_type": "HTTP-01",
Add HTTPS support for the web endpoint with manually configured certificate/key files.
2021-04-23 16:54:35 -04:00
"tls_cert_path": "",
Added acl path key in example config
2021-07-04 07:41:38 -04:00
"tls_key_path": "",
"acl_policy_path": ""
If the configuration file contains relative paths (e.g. in the values for private_key_path or derp_map_path), interpret them as relative to the directory where the config.json file was read from.
2021-04-22 21:10:50 -04:00
}