Application config file
More application types are being currently developed, such as workers, cron jobs, and static frontend sites!
DragonOps’ goal is to make customizing your infrastructure delightful and simple. We have abstracted the more complex pieces of application deployment for you, but, that being said, we also want our users to be able to customize what they care about if they want to!
The application config file can be used to customize your application infrastructure so that it fits your specific needs.
Contents
CI/CD
DragonOps generates CI/CD pipelines for both GitHub and Gitlab out of the box. However, there are many reasons you might choose not to use DragonOps CI/CD:
- You are migrating from existing infrastructure and aren’t ready to pivot to our workflows
- You have a custom CI/CD workflow and deployment pattern you want to maintain
- You want to implement a different deployment pattern than what DragonOps provides
- You are using a provider DragonOps does not yet support
- You don’t have any CI/CD, and aren’t ready to implement one yet
In these cases, it’s still easy to update your application. For each application type, we have provided instructions on how to manually deploy any new application code you have from your local machine. You can check these out here.
Default app config file
By default, running the dragonops app add command will generate a dragonops-<app_name>.yml for an application type of your choice. The example below is for a server app.
This application will have a url, be exposed publicly, run continuously, and host your code on a server.
my_app:
name: my-app
type: app
subtype: web
port: "8080"
health_check_path: /
environments:
- environment: dev_environment
group: preprod_group
- environment: stage_environment
group: preprod_group
cpu: 256
memory: 1024
This config means your application can be deployed to both the dev and stage environments, and uses 256 cpu and 1GB memory for both environments.