Deployments
Automate and manage deployments from GitHub.
How Deployments Work
When a deployment is triggered, Depnix clones the latest commit of your configured branch into a new release directory, runs your install and build commands, then atomically swaps the active release symlink so there is no downtime during the switch.
Automatic Deployments via Webhooks
Depnix registers a GitHub webhook on your repository at creation time. Every push to the configured branch triggers an automatic deployment. You can pause auto-deploy at any time from the application settings.
Only pushes to the branch you configured trigger deployments. Other branches are ignored.
Manual Deployments
Click the Deploy Now button from the application detail page to trigger an immediate deployment of the latest commit on the configured branch, regardless of any recent pushes.
Deployment Hooks
Define shell commands to run at specific points in the deployment pipeline: before install, after install, before build, after build, and after activation. Useful for running database migrations, clearing caches, or restarting queues.
Zero-Downtime Deployments
Depnix uses a release-based directory structure. The new release is fully prepared before being made live via a symlink swap, meaning requests are served by the old release right up until the moment the new one is ready.
Deployment Logs
Every deployment produces a detailed log showing each step: repository clone, dependency install, build command, activation, and hook execution. Failed steps are highlighted in red with the exact error output.
Automatic Rollback on Failure
If any deployment step fails, Depnix automatically keeps the previous release active. Your application continues serving traffic while you diagnose and fix the issue.
Review the deployment log for the exact command that failed and its exit code.