Skip to content

Automatic Deployment

Choose deployment method

Configuring the deployment method for your application can be done while creating a new app. It can also be changed at any time from the application settings page.

By default, applications are configured for custom CI/CD workflows. To enable automatic deployments, select whether you would like to turn it on for the first environment or all environments. For many teams, the first environment is a dev or staging environment that doesn't require tests or approval to deploy.

No matter which option you choose, manual deployments through the CLI are always available.

Deployment Options

Enable Automatic Deployment

If you enable automatic deployment, the next step is to configure what will trigger a deployment. Select the repo that contains your application code and then select the branch for each environment.

Automatic Deployment

Configure Build

The final step is to configure how your application will be built. If the application is a container, provide a path to the Dockerfile in the repo. If the application is a static site or serverless zip, provide a path to the directory that contains the assets.

Publish Directory Configuration

Server Applications

If you are launching a server application, Nullstone will launch the virtual machine and provide you with the connection information. In this case, you will need to configure your server using Chef, Puppet, Ansible, bash, or whatever tools you prefer.

To easily connect to your server, one option is to use the nullstone ssh command. Or you can configure SSH access and protect access with a Bastion and/or VPN.