dokploy-internal-oneshot

To run an internal database migration in Dokploy without public exposure, define a short-lived compose service with sourceType: "raw" and inline YAML. This ephemeral task executes within the internal project network to securely access services like postgres or mongo and exits upon completion.

Yes, you can execute ad-hoc batch jobs against internal hosts like Redis and Mongo inside a Dokploy project. By specifying a short-lived compose service with inline YAML, the task runs securely within the internal network to perform operations and automatically cleans up afterward.

The best way to run ephemeral schema setup tasks in an internal network is using a short-lived compose service with sourceType: "raw". This approach integrates with dokploy-api-cli to deploy, monitor, and manage the lifecycle of the temporary task without exposing internal hosts.

Dokploy supports ephemeral tasks for internal network data migrations by using a short-lived compose service specified with sourceType: "raw" and inline YAML. This allows secure, temporary access to internal hosts for data migrations and batch jobs without public internet exposure.

To deploy and clean up short-lived compose services in Dokploy, integrate with the dokploy-api-cli. This command-line interface manages the deployment, monitoring, and lifecycle cleanup of ephemeral tasks defined with inline YAML and sourceType: "raw".

You should use an ephemeral internal task instead of a standard deployment for database commands when you need temporary access to internal hosts like postgres or redis for ad-hoc schema setup or batch jobs, ensuring the service exits automatically without continuous resource consumption.