Consul - Revision history

Pigs: /* Consul */Use current channel for search.nixos.org link

2025-05-07T16:31:26Z

Consul: Use current channel for search.nixos.org link

← Older revision		Revision as of 16:31, 7 May 2025
Line 8:		Line 8:
	</syntaxhighlight>		</syntaxhighlight>

	But there are some [https://search.nixos.org/options?~~channel=20.09&from=0&size=30&sort=relevance&~~query=services.consul.\|consul specific options] that might be useful.		But there are some [https://search.nixos.org/options?query=services.consul consul specific options] that might be useful.

	Setting up Consul in a production setting is beyond the scope of this wiki, see the consul documentation for particulars.		Setting up Consul in a production setting is beyond the scope of this wiki, see the consul documentation for particulars.

imported>Nix: add Software/Applications subcategory

2021-09-20T05:43:43Z

add Software/Applications subcategory

← Older revision		Revision as of 05:43, 20 September 2021
Line 69:		Line 69:
	systemd.services.haproxy-config.enable = true;		systemd.services.haproxy-config.enable = true;
	</syntaxhighlight>		</syntaxhighlight>

			[[Category:Applications]]

imported>Zhenyavinogradov: mention setting service type for consul to "notify"

2021-05-03T09:54:43Z

mention setting service type for consul to "notify"

← Older revision		Revision as of 09:54, 3 May 2021
Line 11:		Line 11:

	Setting up Consul in a production setting is beyond the scope of this wiki, see the consul documentation for particulars.		Setting up Consul in a production setting is beyond the scope of this wiki, see the consul documentation for particulars.

			One advice is that if you have systemd services depending on Consul via <code>After=consul.service</code>, you may want to switch consul service type no <code>notify</code>, to make sure that dependent services don't try to run until Consul is ready to accept connections:

			<syntaxhighlight lang="nix">
			systemd.services.consul.serviceConfig.Type = "notify";
			</syntaxhighlight>

	== Consul-template ==		== Consul-template ==

imported>Zie: formatting cleanup

2020-11-17T17:17:43Z

formatting cleanup

← Older revision		Revision as of 17:17, 17 November 2020
Line 1:		Line 1:
			== Consul ==
	Consul by Hashicorp is a distributed key/value store along with other things.		Consul by Hashicorp is a distributed key/value store along with other things.

Line 11:		Line 12:
	Setting up Consul in a production setting is beyond the scope of this wiki, see the consul documentation for particulars.		Setting up Consul in a production setting is beyond the scope of this wiki, see the consul documentation for particulars.

	## Consul-template		== Consul-template ==

	currently consul-template is packaged, but does not have nixos options to configure it. Here is an haproxy example that might prove useful:		currently consul-template is packaged, but does not have nixos options to configure it. Here is an haproxy example that might prove useful:

imported>Zie: minor note about the config snippet.

2020-11-17T17:16:32Z

minor note about the config snippet.

← Older revision		Revision as of 17:16, 17 November 2020
Line 17:		Line 17:
	This turns on haproxy with essentially a blank config		This turns on haproxy with essentially a blank config
	then sets up a systemd unit to run haproxy-config, a consul-template service to generate the haproxy configuration from your template.		then sets up a systemd unit to run haproxy-config, a consul-template service to generate the haproxy configuration from your template.

			note, in the configuration below, you will need to change: /path/to/haproxy.consul to the path where your haproxy consul template resides. If you rename the file, be sure to fix the ExecReload line as well.

	<syntaxhighlight lang="nix">		<syntaxhighlight lang="nix">

imported>Zie: Added page about Consul and Consul-template

2020-11-17T17:14:59Z

Added page about Consul and Consul-template

New page

Consul by Hashicorp is a distributed key/value store along with other things.

Setting up Consul can be as easy as:

<syntaxhighlight lang="nix">
services.consul.enable = true;
</syntaxhighlight>

But there are some [https://search.nixos.org/options?channel=20.09&from=0&size=30&sort=relevance&query=services.consul.|consul specific options] that might be useful.

Setting up Consul in a production setting is beyond the scope of this wiki, see the consul documentation for particulars.

## Consul-template

currently consul-template is packaged, but does not have nixos options to configure it. Here is an haproxy example that might prove useful:

This turns on haproxy with essentially a blank config
then sets up a systemd unit to run haproxy-config, a consul-template service to generate the haproxy configuration from your template.

<syntaxhighlight lang="nix">
services.haproxy.enable = true;
services.haproxy.config = "#this should be replaced via systemd.services.haproxy-config";
systemd.services.haproxy-config = {
description = "Consul-Template configuration for HAPROXY.";
documentation = [ "https://github.com/hashicorp/consul-template" ];
wantedBy = [ "multi-user.target" ];
requires = [ "network-online.target" ];
after = [ "network-online.target" "consul.service" ];
path = [
pkgs.coreutils
pkgs.consul
pkgs.consul-template
pkgs.vault
pkgs.cacert
pkgs.procps
];
serviceConfig = {
ExecStart = ''
${pkgs.consul-template}/bin/consul-template -template "/path/to/haproxy.consul:/etc/haproxy.cfg:${pkgs.procps}/bin/pkill -SIGUSR2 haproxy"
'';
ExecReload = "${pkgs.procps}/bin/pkill -HUP -f haproxy.consul";
KillMode = "process";
KillSignal = "SIGINT";
LimitNOFILE = "infinity";
LimitNPROC = "infinity";
Restart = "on-failure";
RestartSec = "2";
StartLimitBurst = "3";
StartLimitIntervalSec="10";
TasksMax = "infinity";
# we run as root, because /etc/ is not writable by the haproxy user, the config file should really exist in /etc/haproxy/
#User = "${config.services.haproxy.user}";
User = "root";
};

environment = {
#systemd environment for haproxy-config
};
};
systemd.services.haproxy-config.enable = true;
</syntaxhighlight>