The process is extremely simple and can be started in just a few seconds by setting two main parameters (i.e. selecting the required repository from Deployment Manager and specifying a target environment). Herewith, deployment can be tuned up to your specific needs by adjusting the additional configs.
Below, we’ve provided a detailed description for all the possible options within the deployment frame:
- Repository – allows to select the Git / SVN project from Deployment Manager (or jump to its addition form)
- Branch – defines the used repository branch (master by default)
- Environment – selects a target environment with the application server (is automatically selected, when installing from application server)
- Path – sets the desired custom context; herewith, the available options may be limited due to the used programming language specifics (e.g. Python and Node.js have a single predefined deployment path only)
- Build (for Java application deployments) – allows to choose the existing Maven build node (or add one into the target environment) and, if required, to select repository Working Directory
- Hooks – applies the provided scripts either before or after deployment process
- Deploy Strategy (for deployments into scaled server) – allows to choose between relatively quicker Simultaneous deployment variant, which causes a brief downtime, and the Sequential deployment with delay option to perform deployment on servers one-by-one with a set delay between operations, which ensures application uptime
- Check and auto-deploy updates – enables periodical check ups for code changes in your repository (with configurable frequency); if any, project automatic deployment is initiated
- Auto-resolve conflicts – prevents the occurrence of merge conflicts by updating the contradictory files to the repository version (i.e. locally made changes are discarded)
- Enable zero-downtime deployment (for PHP servers only) – adjusts the deployment flow to avoid application downtime
Click Deploy to initiate the process.
In a few minutes your application will be successfully deployed. Now, you can access it with the Open in browser button, analyzed via Logs or managed with file manager / via SSH access.