f6bab4f26c
- Renames "Dev" to "Develop" for improved navigation labels - Deployment docs are now located under a larger "Development" section (fewer nav bar choices & realistically I think anyone who wants to do one is going to be referring to the other) - Adds links to tools the first time they're mentioned - Rewords part of the homepage - Hides section navigation on the homepage (now we don't have a blank section nav bar! - Adds some syntax highlighting - Removes some manual word wrapping — this was done very rarely / inconsistently
22 lines
1.1 KiB
Markdown
22 lines
1.1 KiB
Markdown
# Introduction to Deployment
|
|
|
|
Browsertrix Cloud is designed to be a cloud-native application running in Kubernetes.
|
|
|
|
However, despite the name, it is perfectly reasonable (and easy!) to deploy Browsertrix Cloud locally using one of the many available local Kubernetes options. Here are a few recommendations for different scenarios.
|
|
|
|
The main requirements for Browsertrix Cloud are:
|
|
|
|
- A Kubernetes Cluster
|
|
- [Helm 3](https://helm.sh/) (package manager for Kubernetes)
|
|
|
|
We have prepared a [Local Deployment](./local) and [Production (Self-Hosted and Cloud) Deployment](./production) guides to help with
|
|
setting up Browsertrix Cloud for different scenarios.
|
|
|
|
### Non Kubernetes Deployments
|
|
|
|
Previously, Browsertrix Cloud also supported Docker Compose and podman-based deployment. This is now deprecated due to the complexity
|
|
of maintaining feature parity across different setups, and with various Kubernetes deployment options being available and easy to deploy, even on a single machine.
|
|
|
|
Making deployment of Browsertrix Cloud as easy as possible remains a key goal, and we welcome suggestions for how we can further improve our Kubernetes deployment options.
|
|
|