1
0
mirror of https://github.com/oceanprotocol/docs.git synced 2024-11-02 16:25:37 +01:00
docs/content/tutorials/marketplace.md

47 lines
1.4 KiB
Markdown
Raw Normal View History

2018-11-07 12:24:53 +01:00
---
2018-11-07 15:51:17 +01:00
title: Set Up a Marketplace
2020-10-25 17:12:47 +01:00
description:
2018-11-07 12:24:53 +01:00
---
2020-10-25 17:12:47 +01:00
In Ocean, marketplaces and publishers are different roles. A common setup is for one organization to do both. We focus on that here.
2020-10-25 17:12:47 +01:00
## The Steps
2020-10-25 17:12:47 +01:00
1. Develop the first cut of the app.
1. Prepare some initial data assets.
1. Deploy to production.
2020-10-25 17:12:47 +01:00
## Develop a First Cut of the App
2020-10-25 17:12:47 +01:00
Here are some approaches:
- Fork [Ocean Market](/references/market/) code
- Build from [Ocean React hooks](/references/react/).
- Build up from [ocean.js](/references/ocean.js/) or [ocean.py](https://github.com/oceanprotocol/ocean.py) drivers
2020-10-25 17:12:47 +01:00
## Prepare Some Initial Data Assets
2020-10-25 17:12:47 +01:00
When you deploy, you'll want some initial data assets for your market to offer.
2020-10-25 17:12:47 +01:00
Ocean supports several types, such as Azure and S3 storage. The [tutorials](/tutorials/) section provides more info.
2020-10-25 17:12:47 +01:00
## Deploy to Production
2020-10-25 17:12:47 +01:00
When developing your app, you'll likely use Barge to run all the Ocean Protocol components on your local machine.
2020-10-25 17:12:47 +01:00
When it comes time to go to production, you will have to run these components:
- Your marketplace/publisher app
2020-10-25 17:12:47 +01:00
- Aquarius (with Elasticsearch)
- Provider-py
Of course, there are many other things that must be handled in production:
- Security of the infrastructure where the software is running
- Monitoring
- Log aggregation, storage and search
- Handling crashes or other faults
2020-10-25 17:12:47 +01:00
Each of those is beyond the scope of these docs.