Installation Overview
This section describes how to plan, install, and configure Posit Connect. Use this page to find the resources for each stage of the installation.
Connect supports two execution models. In local execution, the Connect service and all published content run on the same host. In off-host execution, Connect builds environments and runs content in containers on a Kubernetes cluster, isolated from the Connect service.
Before you deploy Connect to production, Posit recommends that you set up a separate staging environment that matches your production configuration. Use the staging environment to test upgrades, configuration changes, and new content before you apply them to production.
Also use the staging environment for user acceptance testing (UAT). In UAT, a small group of publishers and viewers deploy and open their own content to make sure that it works as expected.
Step 1: Review pre-installation resources
Review these resources to plan your deployment:
- Sizing and capacity planning: how to size the server for your content and expected traffic.
- Selecting the right architecture: how to choose a deployment architecture for your environment.
- Generic architectures: end-to-end diagrams for local and off-host deployments.
- Requirements: supported Linux distributions, hardware, runtimes, and browsers.
Step 2: Install Connect
Choose the installation method that matches your environment, then follow its steps to install Connect:
| Method | Situation |
|---|---|
| Server installation | Run Connect and all content on a single Linux server. |
| Multi-server installation | Run Connect with high availability and load balancing across multiple Linux servers. |
| Off-host execution | Run content in containers on a Kubernetes cluster, isolated from the Connect service. |
To compare these options with reference diagrams, see Generic architectures.
Step 3: Configure Connect
After you install Connect, see the Initial Configuration page for more settings and verification tasks.