Skip to content

Commit 3263dfc

Browse files
valekjom-murasovs
andauthored
Add note on using environment variables during build (#394)
Co-authored-by: Misha <[email protected]>
1 parent 18fc190 commit 3263dfc

File tree

1 file changed

+2
-0
lines changed

1 file changed

+2
-0
lines changed

content/docs/actors/development/source_code.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -135,6 +135,8 @@ console.log(process.env.SMTP_HOST);
135135

136136
The actor runtime sets additional environment variables for the actor process during the run. See [Environment variables]({{@link actors/development/environment_variables.md}}) for details.
137137

138+
The environment variables can also be used for the build process. In this case, the variables are treated as [Docker build arguments](https://docs.docker.com/engine/reference/builder/#arg). This means that they should not be used for secrets and, in order to access them in Dockerfile, you have to use the `ARG variable_name` instruction.
139+
138140
## [](#versioning)Versioning
139141

140142
In order to enable active development, the actor can have multiple versions of the source code and associated settings, such as the **Base image** and **Environment**. Each version is denoted by a version number of the form `MAJOR.MINOR`; the version numbers should adhere to the [Semantic Versioning](http://semver.org/) logic.

0 commit comments

Comments
 (0)