read-eval example provided in PROFILES.md
This commit is contained in:
parent
39fa6afb52
commit
60e4ef856c
1 changed files with 13 additions and 0 deletions
|
@ -128,6 +128,19 @@ profile, which is the profile used if you don't change it using
|
||||||
`[:dev :provided :user :base]`, but you can change this in your
|
`[:dev :provided :user :base]`, but you can change this in your
|
||||||
`project.clj` just like any other profile.
|
`project.clj` just like any other profile.
|
||||||
|
|
||||||
|
## Using Functions
|
||||||
|
|
||||||
|
Often you want to read an environment variable or execute a function to capture
|
||||||
|
a value to use in your profiles. In order to do such a thing with the profiles.clj
|
||||||
|
you'll need to use the read-eval syntax.
|
||||||
|
|
||||||
|
Here is an example of such a case:
|
||||||
|
|
||||||
|
```clj
|
||||||
|
{:user {:compile-path #=(eval (System/getenv "ci.compile-path")),
|
||||||
|
:target-path #=(eval (System/getenv "ci.target-path"))}}
|
||||||
|
```
|
||||||
|
|
||||||
## Debugging
|
## Debugging
|
||||||
|
|
||||||
To see how a given profile affects your project map, use the
|
To see how a given profile affects your project map, use the
|
||||||
|
|
Loading…
Reference in a new issue