| .. | ||
| compute-to-data-docker-registry.md | ||
| compute-to-data-minikube.md | ||
| deploying-aquarius.md | ||
| deploying-marketplace.md | ||
| deploying-ocean-subgraph.md | ||
| deploying-provider.md | ||
| README.md | ||
| setup-server.md | ||
| description | cover | coverY |
|---|---|---|
| Learn how to deploy Ocean components in your environment. | ../.gitbook/assets/cover/infrastructure_banner.png | 0 |
🔨 Infrastructure
There are many ways in which the components can be deployed, from simple configurations used for development and testing to complex configurations, used for production systems.
All the Ocean Protocol components (Provider, Aquarius, Subgraph) are designed to run in Docker containers, on a Linux operating system. For simple configurations, we rely on Docker Engine and Docker Compose products to deploy and run our components, while for complex configurations we use Kubernetes. The guides included in this section will present both deployment options.
Please note that deploying the Ocean components requires a good understanding of:
- Linux operating system
- Docker Engine
- Docker Compose or Kubernetes (depending on the configuration chosen for the component deployment)
Please note that although Ocean Marketplace is not a core component of our stack but rather an example of what can be achieved with our technology, in this section we included a guide on how to deploy it.
All components need to be deployed on a server, so we included a guide about how to install and configure a server will all the necessary tools.