Deploy Application
Deploy your code changes in smaller chunks to make it easier to validate the code through build and testing pipelines, reducing the feedback loop on error detection. Learn how to use Devopness to deploy application changes confidently, with zero downtime, using your own custom build pipelines and make sure your users can benefit from your application as soon as possible. The more often you deploy your application, the better it tends to improve.
- On Devopness, navigate to a project then select an environment
- Find the
Applicationscard - Click
Viewin theApplicationscard to see a list of existingApplications - Click
DEPLOYon the application you want to deploy - Follow the prompts, then click
Next - Review deploy information then click
ConfirmA notification popup will be displayed, confirming that the deployment has been triggered
- Wait for the
Application:Deployaction to be completed
Now that your application has been deployed, it can be accessed over the internet by setting up a DNS record, or testing access to the application via server IP address.
- For details on how to make an application public, follow the instructions in Add virtual host.
Required Permissions
To complete the steps in this guide, the user needs the following permissions in the environment:
| Resource Type | Permission |
|---|---|
| Application | Deploy |
For instructions on how to grant user permissions in an environment, see Add team to an Environment
Deploy Application using an Incoming Hook
As project users base grow, there's a need to rely more on processes and automation; Devopness helps by providing, among other tools, customizable CI/CD pipelines, empowering our users to automate common and repetitive tasks to improve code quality and their code review processes. Create an incoming webhook to trigger an application deploy programmatically.
Edit an Application
Learn how to edit an application to keep its configuration up to date, specially the settings that define how the application is deployed, such as source provider, repository, dependencies to be installed, directories and the application entrypoint.