Octopus Deploy is made up of two applications, a server and a tentacle. This video gives an overview of the responsibilities of the server and tentacle and how they work together to deploy applications.
- [Instructor] Octopus Deploy is actually made up…of two applications.…The first is the Octopus Server application,…a self-hosted web application that serves up a web front end…which is used to configure Octopus and release applications.…The second is the aptly-named Tentacle application,…a Windows service that runs on the server…you're deploying your application to.…The server orchestrates the release,…the Tentacle does the work.…The Tentacle can be configured in two ways.…It can be a listening Tentacle, in which the Octopus Server…contacts the Tentacle over an open port when it's time…to do the release, or it can be a polling Tentacle.…
If you can't have a port open between your Tentacle…and your Octopus Server application,…a polling Tentacle is the way to go.…If you can have a port open, it's recommended that you go…with the listening Tentacle.…Let's go through an example using a listening Tentacle.…If you're using a listening tentacle…when it's time to release an application,…the Octopus Server contacts the Tentacle,…
- What is Octopus Deploy?
- Working with the Octopus server and tentacles
- Using variables to scope configuration items such as roles and targets
- Installing and configuring Octopus Deploy
- Deploying a sample application
- Configuring a build server, adding a project, and creating a release
- Controlling release flow with life cycles and channels