From 8b717eb001811bc5da5d15d1163565de00b4ffa4 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fl=C3=A1vio=20Sousa?= Date: Mon, 5 Jun 2023 10:13:35 +0100 Subject: [PATCH] Update README.md with BABASHKA_PODS_DIR (#68) --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7d742cc..c390133 100644 --- a/README.md +++ b/README.md @@ -77,7 +77,7 @@ On the JVM: When calling `load-pod` with a string or vector of strings (or declaring it in your `bb.edn`), the pod is looked up on the local file system (either using the PATH, or using an absolute path). When it is called with a qualified symbol and a version - like `(load-pod 'org.babashka/aws "0.0.5")` -then it will be looked up in and downloaded from the [pod-registry](https://github.com/babashka/pod-registry). +then it will be looked up in and downloaded from the [pod-registry](https://github.com/babashka/pod-registry). You can customize the file system location that `load-pod` will use by setting the `BABASHKA_PODS_DIR` environment variable. By default babashka will search for a pod binary matching your system's OS and arch. If you want to download pods for a different OS / arch (e.g. for deployment to servers), you can set one or both of the following