oceanprotocol/docs
1
0
Fork 0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-26 19:49:26 +01:00
Code Releases Activity

GITBOOK-620: Add a starting page to the Infrastructure section

Browse Source
This commit is contained in:
Mihai Badea 2023-06-27 08:29:12 +00:00 committed by gitbook-bot
parent 0a19d09717
commit 71d6bffffc
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
2 changed files with 14 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

13
infrastructure/README.md
View File

@ -6,3 +6,16 @@ coverY: 0
# 🔨 Infrastructure
Now that you know the components of the Ocean Protocol stack and what each does, it's time to learn how to deploy these components in your environment. 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.

6
infrastructure/setup-server.md
View File

@ -6,11 +6,7 @@ description: >-
# Setup a Server
Now that you know the components of the Ocean Protocol stack and what each does, it's time to learn how to deploy these components in your environment. 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 with Docker Engine. 
Each deployment starts with setting up a server on which the component will be installed, either on-premise or hosted in a cloud platform.
Each deployment of the Ocean components starts with setting up a server on which these will be installed, either on-premise or hosted in a cloud platform.
## Prerequisites