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-376: change request with no subject merged in GitBook

Browse Source
This commit is contained in:
enzo 2023-05-31 12:14:46 +00:00 committed by gitbook-bot
parent 84e69bbd81
commit a67c721298
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
2 changed files with 51 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
SUMMARY.md
View File

@ -47,7 +47,7 @@
* [DDO Specification](developers/ddo-specification.md)
* [Storage Specifications](developers/storage-specifications.md)
* [Fine-Grained Permissions](developers/Fine-Grained-Permissions.md)
* [Local Setup - Ganache](developers/local-setup-ganache.md)
* [Local Setup - Barge](developers/local-setup-ganache.md)
* [Build a Marketplace](developers/build-a-marketplace/README.md)
* [Forking Ocean Market](developers/build-a-marketplace/forking-ocean-market.md)
* [Customising a Market](developers/build-a-marketplace/customising-your-market.md)

56
developers/local-setup-ganache.md
View File

@ -1,11 +1,55 @@
# Local Setup - Ganache
---
description: 🧑🏽‍💻 Your Local Development Environment for Ocean Protocol
---
\----WORK in progress----
# Local Setup - Barge
### Local / Ganache
Barge is a powerful tool designed to provide developers with a local development environment for working with Ocean Protocol. It simplifies the setup process by using Docker Compose files to deploy the entire Ocean Protocol stack locally. With Barge, you can quickly set up and run the latest versions of Aquarius, Provider, Ganache, TheGraph, ocean-contracts, and more.
The most straightforward way for local-only development is to use [Barge](https://www.github.com/oceanprotocol/barge), which runs [Ganache](https://www.trufflesuite.com/ganache), Aquarius, and Provider. It is used extensively by the Ocean core devs and for automated integration testing.
**Functionalities of Barge**
To connect to it from MetaMask, select the network called _Localhost 8545_.
Barge offers several functionalities that enable developers to create and test the Ocean Protocol infrastructure efficiently. Here its key components:
Alternatively, you can run Ganache independently. Install it according to [the Ganache docs](https://www.trufflesuite.com/ganache). Then deploy Ocean contracts onto Ganache following [docs in Ocean contracts repo](https://www.github.com/oceanprotocol/contracts). Ganache is at the RPC URL [http://localhost:8545](http://localhost:8545).
| Functionality | Description |
| ------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Aquarius | A metadata storage and retrieval service for Ocean Protocol. Allows indexing and querying of metadata. |
| Provider | A service that facilitates interaction between users and the Ocean Protocol network. |
| Ganache | A local Ethereum blockchain network for testing and development purposes. |
| TheGraph | A decentralized indexing and querying protocol used for building subgraphs in Ocean Protocol. |
| ocean-contracts | Smart contracts repository for Ocean Protocol. Deploys and manages the necessary contracts for local development. |
| Customization and Options | Barge provides various options to customize component versions, log levels, and enable/disable specific blocks. |
Barge makes it easy for developers to get started with Ocean Protocol by providing a comprehensive local development environment. With its modular and user-friendly design, developers can focus on building and testing their applications without worrying about the intricacies of the underlying infrastructure.
To use Barge, you can follow the instructions in the [Barge repository](https://github.com/oceanprotocol/barge).
Before getting started, make sure you have the following prerequisites:
* Linux or macOS operating system. Barge does not currently support Windows, but you can run it inside a Linux virtual machine or use the Windows Subsystem for Linux (WSL).
* Docker installed on your system. You can download and install Docker from the [Docker website](https://www.docker.com/get-started). On Linux, you may need to allow non-root users to run Docker. On Windows or macOS, it is recommended to increase the memory allocated to Docker to 4 GB (default is 2 GB).
* Docker Compose, which is used to manage the Docker containers. You can find installation instructions in the [Docker Compose documentation](https://docs.docker.com/compose/).
Once you have the prerequisites set up, you can clone the Barge repository and navigate to the repository folder using the command line:
```bash
git clone git@github.com:oceanprotocol/barge.git
cd barge
```
The repository contains a shell script called `start_ocean.sh` that you can run to start the Ocean Protocol stack locally for development. To start Barge with the default configurations, simply run the following command:
```bash
./start_ocean.sh
```
This command will start the default versions of Aquarius, Provider, and Ganache, along with the Ocean contracts deployed to Ganache.
For more advanced options and customization, you can refer to the README file in the Barge repository. It provides detailed information about the available startup options, component versions, log levels, and more.
To clean up your environment and stop all the Barge-related containers, volumes, and networks, you can run the following command:
```bash
./cleanup.sh
```
Please refer to the Barge repository's README for more comprehensive instructions, examples, and details on how to use Barge for local development with the Ocean Protocol stack.