Enable zero-downtime deployment (for PHP servers only) - adjusts the deployment flow to avoid application downtime.Auto-resolve conflicts - prevents the occurrence of merge conflicts by updating the contradictory files to the repository version (i.e.

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.

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.

Branch - defines the used repository branch ( master by default).

Repository - allows to select the Git / SVN project from Deployment Manager (or jump to its addition form).

Herewith, deployment can be tuned up to your specific needs by adjusting the additional configs.

selecting the required repository from Deployment Manager and specifying a target environment). The process is extremely simple and can be started in just a few seconds by setting two main parameters (i.e. Enable zero-downtime deployment (for PHP servers only) - adjusts (if option is ticked) the deployment flow to avoid application downtimeĬlick Deploy to initiate the process itself.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.Hooks - applies the provided scripts either before or after deployment process.Python and Node.js have a single predefined deployment path only) Path - sets the desired custom context herewith, the available options may be limited due to the used programming language specifics (e.g.Environment - selects a target environment with the application server (is automatically selected, when installing from application server).Local file (or URL) - points to the archive file to be deployed (is automatically selected, when installing from Deployment Manager).Herewith, deployment can be tuned up to your specific needs by adjusting the additional configs.īelow, we’ve provided a detailed description for all the possible options within the deployment frame:

providing required archive and specifying a target environment). NET deployment process for the Windows-based IIS application server is different from the standardized flow described in this guide the VCS deployment type for Java application servers is performed with a help of the Maven build node, refer to the linked guide for additional details.Choose the appropriate option and click it to proceed with your deployment configuration. The first two icons ( Local file and URL) corresponds to deployment via archive and the last one ( Git / SVN) - to deployment from the VCS repository. They can be called either from Deployment Manager or by hovering over the Deployments record, which is provided for all application servers, and clicking one of the appropriate buttons. Hub Registry - creates a custom container with your application based on the Docker image stored at your public or private registryįor more information on the last two options, use the appropriate links, while in this guide we’ll describe deployment via archive and VCS repository.VCS - allows to deploy from your VCS repository (e.g.Dashboard - corresponds to deployment via archive (provided either as local file or URL).The platform supports various ways of the applications automatic deployment, allowing to choose the most suitable option, which will suit your specific needs:

Remote development netbeans 8.2