Michael Schurter 30db07cccb docs: sync systemd unit files; update deploy guide ... The systemd configs spread across our repo were fairly out of sync. This should get them on our best practices. The deployment guide also had some strange things like running Nomad as a non-root user. It would be fine for servers but completely breaks clients. For simplicity I simply removed the non-root user references.		2019-03-19 15:18:12 -07:00
..
consul-template.hcl	AWS env update (#5423)	2019-03-15 15:55:34 -04:00
consul-template.service	AWS env update (#5423)	2019-03-15 15:55:34 -04:00
consul.json	update Consul config files to use updated retry-join syntax	2017-11-01 21:09:07 +00:00
consul_aws.service	update config files to support systemd and Azure; reorganize Packer file hierarchy; update Vagrantfile to use latest tool versions	2017-11-15 19:31:46 +00:00
consul_azure.service	update config files to support systemd and Azure; reorganize Packer file hierarchy; update Vagrantfile to use latest tool versions	2017-11-15 19:31:46 +00:00
consul_client.json	update Consul config files to use updated retry-join syntax	2017-11-01 21:09:07 +00:00
core-site.xml	refactor build and provisioning scripts to support DNS integration, HDFS	2017-06-24 16:25:46 -07:00
nomad.hcl	Corrected vault address and port in client/server hcl	2018-09-14 16:18:03 +00:00
nomad.service	docs: sync systemd unit files; update deploy guide	2019-03-19 15:18:12 -07:00
nomad_client.hcl	Corrected vault address and port in client/server hcl	2018-09-14 16:18:03 +00:00
vault.hcl
vault.service	update config files to support systemd and Azure; reorganize Packer file hierarchy; update Vagrantfile to use latest tool versions	2017-11-15 19:31:46 +00:00