diff --git a/public/docs/i/1000/installation/octopus-install-diagram.webp b/public/docs/i/1000/installation/octopus-install-diagram.webp new file mode 100644 index 0000000000..96388f3cc9 Binary files /dev/null and b/public/docs/i/1000/installation/octopus-install-diagram.webp differ diff --git a/public/docs/i/2000/installation/octopus-install-diagram.webp b/public/docs/i/2000/installation/octopus-install-diagram.webp new file mode 100644 index 0000000000..a0ee2584e3 Binary files /dev/null and b/public/docs/i/2000/installation/octopus-install-diagram.webp differ diff --git a/public/docs/i/600/installation/octopus-install-diagram.webp b/public/docs/i/600/installation/octopus-install-diagram.webp new file mode 100644 index 0000000000..01a4f2e123 Binary files /dev/null and b/public/docs/i/600/installation/octopus-install-diagram.webp differ diff --git a/public/docs/i/x/installation/octopus-install-diagram.png b/public/docs/i/x/installation/octopus-install-diagram.png new file mode 100644 index 0000000000..f86651b528 Binary files /dev/null and b/public/docs/i/x/installation/octopus-install-diagram.png differ diff --git a/public/docs/img/installation/octopus-install-diagram.png b/public/docs/img/installation/octopus-install-diagram.png new file mode 100644 index 0000000000..c7e70933a3 Binary files /dev/null and b/public/docs/img/installation/octopus-install-diagram.png differ diff --git a/public/docs/img/installation/octopus-install-diagram.png.json b/public/docs/img/installation/octopus-install-diagram.png.json new file mode 100644 index 0000000000..a5c092b55e --- /dev/null +++ b/public/docs/img/installation/octopus-install-diagram.png.json @@ -0,0 +1 @@ +{"width":2145,"height":1419,"updated":"2026-05-07T22:28:53.266Z"} \ No newline at end of file diff --git a/src/pages/docs/best-practices/self-hosted-octopus/high-availability.mdx b/src/pages/docs/best-practices/self-hosted-octopus/high-availability.mdx index 2df2547e4f..5c12d10c47 100644 --- a/src/pages/docs/best-practices/self-hosted-octopus/high-availability.mdx +++ b/src/pages/docs/best-practices/self-hosted-octopus/high-availability.mdx @@ -30,6 +30,10 @@ An Octopus High Availability configuration requires four main components: One of the benefits of High Availability is the database and file storage is running on a separate infrastructure from the Octopus Server service. For a production instance, we recommend everyone follow the steps below, even if you plan on running a single node instance. If anything were to happen to that single node, you could be back up and running quickly with a minimal amount of effort. In addition, adding a second node later will be much easier. ::: +:::figure +![Octopus Deploy Self-Hosted Reference Diagram](/docs/img/installation/octopus-install-diagram.png) +::: + This implementation guide will help configure High Availability. If you are looking for an in-depth set of recommendations, please refer to our white paper on [Best Practices for Self-Hosted Octopus Deploy HA/DR](https://octopus.com/whitepapers/best-practice-for-self-hosted-octopus-deploy-ha-dr). ## How High Availability Works diff --git a/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx b/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx index 3da0374be3..16fd436f79 100644 --- a/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx +++ b/src/pages/docs/best-practices/self-hosted-octopus/installation-guidelines.mdx @@ -21,6 +21,10 @@ There are three components to an Octopus Deploy instance: - **SQL Server Database** Most data used by the Octopus Server nodes is stored in this database. - **Files or BLOB Storage** Some larger files - like [packages](/docs/packaging-applications/package-repositories), artifacts, and deployment task logs - aren't suitable to be stored in the database and are stored on the file system instead. This can be a local folder, a network file share, or a cloud provider's storage. +:::figure +![Octopus Deploy Self-Hosted Reference Diagram](/docs/img/installation/octopus-install-diagram.png) +::: + This document will provide you with guidelines and recommendations for self-hosting Octopus Deploy. diff --git a/src/pages/docs/installation/index.mdx b/src/pages/docs/installation/index.mdx index a1ae0e5474..c11c22330d 100644 --- a/src/pages/docs/installation/index.mdx +++ b/src/pages/docs/installation/index.mdx @@ -33,6 +33,10 @@ All inbound traffic to Octopus Deploy is via: For production instances of Octopus Deploy, it is best to configure a [load balancer](/docs/installation/load-balancers) to route traffic to your instance. Leveraging a load balancer offers numerous benefits, such as redirecting users to a maintenance page while the instance is down for upgrading, as well as making it much easier to configure High Availability later. +:::figure +![Octopus Deploy Self-Hosted Reference Diagram](/docs/img/installation/octopus-install-diagram.png) +::: + ## Self-hosted Octopus Server When installed, the self-hosted Octopus Server: