Add an Application

Add applications to your infrastructure environments so they can be managed and deployed directly by web interface or through automated workflows

1. On Devopness, navigate to a project then select an environment
2. Find the Applications card
3. Click View in the Applications card to see a list of existing Applications
4. On the upper-right corner of the list click ADD APPLICATION
5. Select a Source Provider
6. Select a Credential

   If no credential is listed or you want to use a different one, click Create a new Credential and follow the guide Add credential

7. Once a Credential is selected, select the git repository where the application source code is hosted
8. Follow the prompts then click CONFIRM
9. In the Application details view, the recently created Application details can be seen

Multiple repositories in the same environment

You can add unlimited applications to the same environment, one per repository. This works well when your marketing site, demo app, production app, API, AI agents, and MCP servers belong to the same product and are managed by the same teams.

If you later need to separate demo and production (separate domains, versions, data, or access rules), create a new environment and deploy those applications there.

Enable auto deployments on git push

To deploy automatically when you push commits, set up an incoming webhook in Devopness and connect it to your Git provider. This is currently done via the API (not the UI yet).

Steps:

1. Create an incoming webhook in Devopness
   • Follow the guide Create incoming webhook
2. Add a webhook in your GitHub repository using the incoming webhook URL and secret
3. Push a commit to verify the deployment triggers

Keep apps running in the background

If your application is not managed by Docker Compose, add a daemon to keep it running and auto-restart it. For a Next.js application, the command is typically npm run start.

1. Add a daemon with the start command and working directory
   • Follow the guide Add daemon

Redeploy after configuration changes

If you change configuration files (for example a .env file), run a new deployment so the updated configuration is applied. Follow the guide Run pipeline.