0a1f5eff8e
* Add stylesheet & mkdocs features - Adds a custom stylesheet & brand colours - Adds Recursive as the code font - Adds repo info to the nav bar - Adds auto tracking ID links for deep linking to sections as users scroll the page - Index pages are now a part of their section as determined by their H1 - Removes mkdocs info from future footer * Reorganize content - Renames "Dev" to "Develop" for improved navigation labels - 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 * Rename "Developer Docs" index page - Better title for sidebar * Update docs.md - Adds links to tools - Adds future docs style guide section - Updates name and makes it an H1 - Replaces hyphens on the homepage with em dashes * deployment index page: changed title, removed non-k8s section, cleaned up intro * develop index page: changed title fixed typo on main page --------- Co-authored-by: Ilya Kreymer <ikreymer@gmail.com>
16 lines
717 B
Markdown
16 lines
717 B
Markdown
# Deploying Browsertrix Cloud
|
|
|
|
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.
|
|
|
|
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 Guide](./local) which covers several options for testing Browsertrix Cloud locally on a single machine,
|
|
as well as a [Production (Self-Hosted and Cloud) Deployment](./production) guides to help with
|
|
setting up Browsertrix Cloud for different production scenarios.
|