Your Ideas

## Background We have an orchestration tool that can create and configure EC2 instances that are uniform with other instances. As the final steps, we'd need to add them to deploybot environment as a server and trigger a deployment. This could be done via the API, and using a template as described here: https://deploybot.canny.io/your-ideas/p/template-servers-configuration Once the server was added, and a deployment is successful, we could complete the new instance addition by registering them at the load balancer ## Feature Create a new server within an existing environment Specify the server IP Specify the template OR specify all the server details

This is a bit of a different use case. But essentially, if we want to deploy a fresh server with a certain configuration. E.g. a LEMP stack, Node, postgres, mysql, docker etc. So we could have a deployment for each type, that does not have any GIT repo attached. Connect a fresh server and let it go through the configuration steps we have specified. This would maybe make sense to be a separate feature. Like a saved server configurations similar to how the containers work.

Allow setting a different notification for successful deployments and unsuccessful deployments. E.g. For errors, we might want notifications to be handled differently than for successful ones.

Allow the sentry integration to work with self-hosted instances. https://github.com/getsentry/self-hosted

Allow connecting public GIT repos for deployments. The use case for this, is if we want to deploy and configure a fresh deployment of an open source project, pre-configured to our liking (via config files and terminal commands). Could potentially allow for pulling updates and deploying them also.

This would be great as it would unlock countless other systems for receiving notifications as well as triggering other actions.