The first step would be to get a grasp of the fundamentals of Octopus:
Next, take a deeper dive into configuring your deployment targets:
- Deployment Targets
- Linux Overview - Discover which distributions are supported.
- Linux Tentacle - This is the recommended way to configure Linux deployment targets.
- Linux SSH Targets - An alternative to the Linux tentacle that does not require an agent to be installed.
- SSH key pair account - Securely store SSH keys in Octopus.
- Kubernetes deployment targets - Configure Kubernetes cluster targets.
Look at the type of deployments you’d like to do:
- Java applications - Documentation & Blogs
- Node Deployments
- NGINX Deployments
- MySQL flyway deployments
- Structured configuration variables - define variables in Octopus for use in JSON, YAML, XML, and Properties configuration files of your applications.
- Spring configuration strategies across environments
- Packaging your application
- Deployment Patterns
- Build a tutorial for your CI/CD stack
- As an alternative to deployments, you can use runbooks.
- Execution containers for workers - For a process step running on a worker or the Octopus Server, you can select a Docker image to execute the step inside of.
If you want to script tasks or interact with Octopus from the terminal, you can call the REST API and CLI:
- Octopus CLI
- API Documentation
- Webinar recording: Using the Octopus API to save time by automating repetitive tasks
You can use our Octopus Server Linux container to spin up a free local instance for testing during development.
Finally, as an aside, it may interest you to know that we run Octopus Cloud on Linux; this article explains the reasons we selected to run a Linux container in Kubernetes.