Dokploy/website
1
0
Fork 0
mirror of https://github.com/Dokploy/website.git synced 2026-06-15 20:25:25 +02:00
Code Issues Packages Projects Releases Wiki Activity

docs: add environment variables section for Dockerfile builds

Browse Source 
- Introduced a new section detailing the configuration of build time arguments and build-time secrets for Dockerfile builds.
- Explained the importance of using build-time secrets for sensitive information and provided links to relevant Docker documentation.
- Added a callout emphasizing best practices for handling sensitive data during the build process.
This commit is contained in:
Mauricio Siu
2025-12-07 12:52:15 -06:00
parent 9da77b4ac7
commit 102e53a629
2 changed files with 14 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
apps/docs/content/docs/core/applications/advanced.mdx
View File

@@ -3,7 +3,7 @@ title: Advanced
description: Learn how to use advanced features in your application.
---
This section is designed for experienced users who need to manage complex configurations and orchestration settings in Dokploy. Here, you can execute custom commands, manage cluster replicas, select Docker registries, and configure Docker Swarm settings.
This section is designed for experienced users who need to manage complex configurations and orchestration settings in Dokploy. The **Advanced** tab is located in your **Applications** settings. Here, you can execute custom commands, manage cluster replicas, select Docker registries, and configure Docker Swarm settings.
### Run Command
@@ -13,7 +13,7 @@ This section is designed for experienced users who need to manage complex config
### Cluster Settings
- **Purpose**: Manages the scaling and distribution of the application across multiple servers or nodes.
- **Replicas**: Set the number of instances of your application that should be running.
- **Replicas**: Set the number of instances of your **application** that should be running.
- **Registry Selection**: Choose the Docker registry from which your container images will be pulled. This is crucial for ensuring that the correct images are used during deployment.
#### Important Note

12
apps/docs/content/docs/core/applications/build-type.mdx
View File

@@ -70,6 +70,18 @@ Dokploy expose 3 Fields to be configured:
- `Docker Context Path`: This is where the Dockerfile is located, eg. If your Dockerfile is in the root of your application you can just specify the `.` (dot) character, is basically to tell docker what context will use to build your application, you can read [Dockerfile Context](https://docs.docker.com/build/concepts/context/) for more information.
- `Docker Build Stage`: This is the build stage to use for building the application, eg. If you want to use the `builder` stage you can specify the `builder` stage, read more about build stages [here](https://docs.docker.com/build/building/multi-stage/).
#### Environment Variables for Dockerfile Builds
When you enable the Dockerfile build type, two additional fields become available in the **Environment** tab:
- **Build Time Arguments**: Configure [build arguments (ARG)](https://docs.docker.com/build/building/variables/) that are passed to your Dockerfile during the build process. Build arguments allow you to parameterize your Dockerfile, making it more flexible and reusable. For example, you can specify versions of dependencies, feature flags, or other build-time configurations.
- **Build-time Secrets**: Configure [build secrets](https://docs.docker.com/build/building/secrets/) to securely pass sensitive information (such as API tokens, passwords, or SSH keys) to your build process. Unlike build arguments, secrets are not exposed in the final image or build history, making them the recommended way to handle sensitive data during builds.
<Callout type="info">
Build arguments and environment variables are inappropriate for passing secrets, as they persist in the final image. Always use build-time secrets for sensitive information like API tokens or passwords.
</Callout>
### Buildpack