A Deployment is the instantiation of a Blueprint. Think Class-Object relationship from OO concepts.
So, when you define a Blueprint, you're defining your tech stack (Think definition of stagging server). But it's just a definition. The real magic happens when you Deploy a Blueprint. So, when you deploy a Blueprint, a new Deployment is created. Deployment is what represents the actual tech stack live in the cluster. So, say you want to deploy your
feautre-branch of the the
React UI app (from the airbnb example) in your tech-stack. You can customize the default tag of the
React UI Container. And, now Dockup will spin up the whole tech stack with `React UI` having your feature branch.
Delete at: You can decide when you want to delete the deployment, when you are creating one.
Hibernate/Wake Up At: You can set the hibernate/wake up times for all deployments. Dockup will hibernate and wake up the deployments at the set time.
Hibernate/Wake Up: You can hibernate/wake up a paritcular deployment.
logs: You can view logs of a particular container right from the Dockup UI.
Reload: You can reload a paritcular container. So, say you viewed the UI and found a simple typo, but you don't want to create a new deployment, so you make a commit, and reload that particular container.
Delete: You can delete a Deployment. Note that you can't undo this action.
Queued: Deployment is queued for deploying
Starting: Containers are starting up
Started: Containers have started (deployment might not be active yet still)
Deployed: Deployment is Deployed and Active (this is the final state when creating deployment)
Hibernating: Hibernating the deployments
Hibernated: Deployment is hibernated
Waking Up: Waking up the deployment
Deleting: Deleting deployment
Deleted: Deployment deleted (this is the final state)
Failed: Deployment failed (more likely, one of the Container failed)
Unready: Containers are in unready state (probably Health Check at work)