mirror of
https://github.com/oceanprotocol/docs.git
synced 2024-11-02 16:25:37 +01:00
46 lines
1.4 KiB
Markdown
46 lines
1.4 KiB
Markdown
---
|
|
title: Set Up a Marketplace
|
|
description:
|
|
---
|
|
|
|
In Ocean, marketplaces and publishers are different roles. A common setup is for one organization to do both. We focus on that here.
|
|
|
|
## The Steps
|
|
|
|
1. Develop the first cut of the app.
|
|
1. Prepare some initial data assets.
|
|
1. Deploy to production.
|
|
|
|
## Develop a First Cut of the App
|
|
|
|
Here are some approaches:
|
|
-Fork [Ocean Market](/references/market/) code
|
|
-Do the [React App Tutorial](/tutorials/react-setup/) then grow your app from there. It uses [Ocean React hooks](/references/react/).
|
|
-Build up from [ocean.js](/references/ocean.js/) or [ocean.py](/references/ocean.py/) drivers
|
|
|
|
## Prepare Some Initial Data Assets
|
|
|
|
When you deploy, you'll want some initial data assets for your market to offer.
|
|
|
|
Ocean supports several types, such as Azure and S3 storage. The [tutorials](/tutorials/) section provides more info.
|
|
|
|
|
|
## Deploy to Production
|
|
|
|
When developing your app, you'll likely use Barge to run all the Ocean Protocol components on your local machine.
|
|
|
|
When it comes time to go to production, you will have to run these components:
|
|
|
|
- Your marketplace/publisher app
|
|
- 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
|
|
|
|
Each of those is beyond the scope of these docs.
|