Prerequisites

1. You must have a Stacktape account. If you don't have an account, please sign up

2. You must have an AWS account connected to your Stacktape organization. Connecting your account takes ~2 minutes. You can connect the account on AWS accounts page in the console

Push-to-deploy deployments

This option is very straightforward. To configure push-to-deploy automatic deployments:

• Navigate to the project you want to be automatically deployed.

• Click on the actions button, and then select View Git configuration

• Click on the Set up Push-To-Branch deployments

• In the modal window, configure the desired properties for the stage (environment) you want to be deployed automatically.

• At this point, every push to the git branch you've configured will trigger a Stacktape deployment.

Preview deployments

Preview deployments are slightly more complicated than push-to-deploy deployments.

They are a great option if you want to validate changes being merged to the selected branch. They can be used to quickly run tests on the stack that is being merged.

Preview deployments are also a great choice if you want to test changes to the frontend of your app. Both your manual testers and your marketing team will have a deployed version that they can then test and immediately see in action.

• Navigate to the project you want to configure preview deployments for.

• Click on the actions button, and then select View Git configuration

• Click on the Set up PR deployments

• In the modal window, configure the desired properties for the stage (environment) you want all of your preview stages to have.

• At this point, if you create a pull request to the configured branch, Stacktape will automatically deploy it. Stacktape will also automatically create a comment inside the PR that shows some properties of the deployed stage - including a link (URL) to all of the internet-accesible resources within that stack (if any).