You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: readme.md
+14-2Lines changed: 14 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ git2consul takes one or many git repositories and mirrors them into [Consul](htt
15
15
#### Requirements / Caveats
16
16
17
17
* git2consul does most of its Git work by shelling out to git. Git must be installed and on your path.
18
-
* git2consul does the rest of its work by calling Consul's REST API. A Consul agent must be running on localhost.
18
+
* git2consul does the rest of its work by calling Consul's REST API.
19
19
* git2consul requires write access to the KV store of its Consul agent.
20
20
* git2consul has only been tested on Unix.
21
21
@@ -42,18 +42,30 @@ The most minimalistic viable git2consul configuration mirrors a single git repo
42
42
}
43
43
```
44
44
45
-
Put that configuration in a file called `/tmp/git2consul.json`. From the git2consul directory, upload that JSON file into the KV as your git2consul config:
45
+
Put that configuration in a file called `/tmp/git2consul.json`. From the git2consul directory, upload that JSON file into the local KV as your git2consul config:
git2consul will now poll the "dev" branch of the "git2consul_data.git" repo once per minute. On first run, it will mirror the 3 files into your Consul K/V with keys:
0 commit comments