From da68e3efd3ee64cb506284a898777ef47c11767d Mon Sep 17 00:00:00 2001 From: Troy McConaghy Date: Fri, 28 Jun 2019 10:42:36 +0200 Subject: [PATCH 1/3] Update the URLs of some components in Nile --- content/concepts/testnets.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/content/concepts/testnets.md b/content/concepts/testnets.md index 539f5514..dc675830 100644 --- a/content/concepts/testnets.md +++ b/content/concepts/testnets.md @@ -42,14 +42,14 @@ There is a Nile blockchain explorer at [https://submarine.dev-ocean.com/](https: There are several Ocean Protocol software components that are live, connected to the Nile Testnet, and operated by BigchainDB GmbH: -- Secret Store at [https://secret-store.dev-ocean.com](https://secret-store.dev-ocean.com) -- Aquarius at [https://nginx-aquarius.dev-ocean.com](https://nginx-aquarius.dev-ocean.com) -- Brizo at [https://nginx-brizo.dev-ocean.com](https://nginx-brizo.dev-ocean.com) +- Secret Store at [https://secret-store.nile.dev-ocean.com](https://secret-store.nile.dev-ocean.com) +- Aquarius at [https://aquarius.nile.dev-ocean.com/](https://aquarius.nile.dev-ocean.com/) +- Brizo at [https://brizo.nile.dev-ocean.com/](https://brizo.nile.dev-ocean.com/) - Jupyter Hub at [https://mantaray.dev-ocean.com](https://mantaray.dev-ocean.com) -- Commons Marketplace at [https://commons.oceanprotocol.com](https://commons.oceanprotocol.com) +- Commons Marketplace at [https://commons.nile.dev-ocean.com](https://commons.nile.dev-ocean.com) - Aquarius for Commons Marketplace at [https://aquarius.marketplace.dev-ocean.com](https://aquarius.marketplace.dev-ocean.com) - Brizo for Commons Marketplace at [https://brizo.marketplace.dev-ocean.com](https://brizo.marketplace.dev-ocean.com) -- Faucet Server at [faucet.nile.dev-ocean.com](https://faucet.nile.dev-ocean.com) +- Faucet Server at [https://faucet.nile.dev-ocean.com](https://faucet.nile.dev-ocean.com) > Internal note: The private "atlantic" repo documents the internal details of the Nile Testnet in `networks/nile/README.md`. From cd8f464a6fd4620ceb753739ac7ffa83cdb03cdc Mon Sep 17 00:00:00 2001 From: Troy McConaghy Date: Fri, 28 Jun 2019 11:00:05 +0200 Subject: [PATCH 2/3] Fix Nile component URLs in other places --- README.md | 4 ++-- gatsby-node.js | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 823244a5..41d98b2a 100644 --- a/README.md +++ b/README.md @@ -197,8 +197,8 @@ The sidebar for those generated reference pages will automatically switch to inc Reference pages based on Swagger specs are sourced from remotely hosted Swagger specs: -- [`https://nginx-aquarius.dev-ocean.com/spec`](https://nginx-aquarius.dev-ocean.com/spec) -- [`https://nginx-brizo.dev-ocean.com/spec`](https://nginx-brizo.dev-ocean.com/spec) +- [`https://aquarius.nile.dev-ocean.com/spec`](https://aquarius.nile.dev-ocean.com/spec) +- [`https://brizo.nile.dev-ocean.com/spec`](https://brizo.nile.dev-ocean.com/spec) They are fetched and updated automatically upon every site build. For more information about stylistic issues, take a look at the section in the test page: diff --git a/gatsby-node.js b/gatsby-node.js index 59e8087a..a55a94b7 100755 --- a/gatsby-node.js +++ b/gatsby-node.js @@ -251,7 +251,7 @@ const createTypeDocPage = async (createPage, name, downloadUrl) => { // https://github.com/swagger-api/swagger-js const fetchSwaggerSpec = async name => { try { - const client = await Swagger(`https://nginx-${name}.dev-ocean.com/spec`) + const client = await Swagger(`https://${name}.nile.dev-ocean.com/spec`) return client.spec // The resolved spec // client.originalSpec // In case you need it From 22ac12b0c15c07d5e349d699d44e967fa7f3dbfa Mon Sep 17 00:00:00 2001 From: Jernej Pregelj Date: Mon, 1 Jul 2019 14:33:36 +0200 Subject: [PATCH 3/3] fix asset, versions --- content/tutorials/react-publish-data-set.md | 3 +-- content/tutorials/react-setup.md | 8 ++++---- content/tutorials/wallets-and-ocean-tokens.md | 2 +- 3 files changed, 6 insertions(+), 7 deletions(-) diff --git a/content/tutorials/react-publish-data-set.md b/content/tutorials/react-publish-data-set.md index 44b13438..97c6c48e 100644 --- a/content/tutorials/react-publish-data-set.md +++ b/content/tutorials/react-publish-data-set.md @@ -27,8 +27,7 @@ const asset = { dateCreated: '2012-02-01T10:55:11Z', author: 'Mario', license: 'CC0: Public Domain', - contentType: 'jpg/txt', - price: 10, + price: '10', files: [ { index: 0, diff --git a/content/tutorials/react-setup.md b/content/tutorials/react-setup.md index 4280789b..f802e8ef 100644 --- a/content/tutorials/react-setup.md +++ b/content/tutorials/react-setup.md @@ -16,9 +16,9 @@ description: This tutorial shows how you can build a basic [React](https://react - Use the startup script in Barge to run a [local Spree Testnet](https://docs.oceanprotocol.com/concepts/testnets/#a-spree-testnet-for-local-development): ```bash - export KEEPER_VERSION=v0.9.1 && \ - export AQUARIUS_VERSION=v0.2.2 && \ - export BRIZO_VERSION=v0.3.5 && \ + export KEEPER_VERSION=v0.10.3 && \ + export AQUARIUS_VERSION=v0.3.5 && \ + export BRIZO_VERSION=v0.3.12 && \ ./start_ocean.sh --no-pleuston ``` @@ -42,7 +42,7 @@ This will create a folder named `marketplace` with a boilerplate React app. Go i ```bash cd marketplace/ -npm install @oceanprotocol/squid@0.5.6 +npm install @oceanprotocol/squid@0.6.2 ``` At this point you can already run `npm start` which starts the app in your browser at [localhost:3000](http://localhost:3000): diff --git a/content/tutorials/wallets-and-ocean-tokens.md b/content/tutorials/wallets-and-ocean-tokens.md index fb4801e3..9fe75580 100644 --- a/content/tutorials/wallets-and-ocean-tokens.md +++ b/content/tutorials/wallets-and-ocean-tokens.md @@ -16,7 +16,7 @@ If you don't see any Ocean Tokens in your crypto wallet software (e.g. MetaMask If the above addresses are out-of-date, then you can find newer ones in the [keeper-contracts repository on GitHub](https://github.com/oceanprotocol/keeper-contracts): -1. Click on the "Branch: **develop**" button and switch to the tag of the latest release (e.g. `v0.8.6`). +1. Click on the "Branch: **develop**" button and switch to the tag of the latest release (e.g. `v0.10.3`). 1. In the `README.md` file, check the address of the OceanToken contract (in Nile or Kovan). 1. Double-check the address by looking in the file named `zos.kovan.json` (for Kovan) or `zos.dev-8995.json` (for Nile). Search for `/OceanToken`. There should be one result and the text around it should look like: