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
@@ -88,7 +88,21 @@ In our Docker-based example, we install `jf` by adding these lines to our `Docke
88
88
RUN curl -fL https://install-cli.jfrog.io | sh && chmod 755 $(which jf)
89
89
```
90
90
91
-
and use this `coder_agent` block:
91
+
## Configuring Coder workspace to use JFrog Artifactory repositories
92
+
93
+
Create a `locals` block to store the Artifactory repository keys for each package manager you want to use in your workspace. For example, if you want to use artifactory repositories with keys `npm`, `pypi`, and `go`, you can create a `locals` block like this:
94
+
95
+
```hcl
96
+
locals {
97
+
artifactory_repository_keys = {
98
+
npm = "npm"
99
+
python = "pypi"
100
+
go = "go"
101
+
}
102
+
}
103
+
```
104
+
105
+
To automatically configure `jf` CLI and Artifactory repositories for each user, add the following lines to your `startup_script` in the `coder_agent` block:
Now, your developers can run `pip install` and transparently use Artifactory as the package registry. You can verify that `pip` is configured correctly by running `pip install --verbose requests` and checking that pip is only hitting your Artifactory URL.
215
+
216
+
## Configuring Go
217
+
218
+
Add the following environment variable to your `coder_agent` block to configure `go` to use Artifactory:
You can apply the same concepts to Docker, Maven, and other package managers
227
+
supported by Artifactory. See the [JFrog documentation](https://jfrog.com/help/r/jfrog-artifactory-documentation/package-management) for more information.
0 commit comments