Skip to content
This repository has been archived by the owner on Mar 8, 2020. It is now read-only.

Commit

Permalink
Remove all @next and :next references from docs (#3711)
Browse files Browse the repository at this point in the history
Signed-off-by: Simon Stone <sstone1@uk.ibm.com>
  • Loading branch information
Simon Stone authored Mar 28, 2018
1 parent dd8ad3b commit c7e94a6
Show file tree
Hide file tree
Showing 5 changed files with 12 additions and 13 deletions.
2 changes: 1 addition & 1 deletion packages/composer-website/jekylldocs/_data/links.yml
Original file line number Diff line number Diff line change
@@ -1,3 +1,3 @@

playground:
https://composer-playground-next.mybluemix.net
https://composer-playground.mybluemix.net
Original file line number Diff line number Diff line change
Expand Up @@ -23,22 +23,21 @@ These instructions assume that you've not installed the tools and used them befo
> To provide flexibility and enable the maximum number of dev, test and deployment scenarios, {{site.data.conrefs.composer_short}} is delivered as a set of components you can install with `npm` and control from the CLI. These instructions will tell you how to install everything first, then how to control your development environment.
# Installing components
Please note the `@next` in the npm install commands. This is important to ensure you install the appropriate version to work with {{site.data.conrefs.hlf_full}} {{site.data.conrefs.hlf_latest}}.

### Step 1: Install the CLI tools
There are a few useful CLI tools for {{site.data.conrefs.composer_short}} developers. The most important one is `composer-cli`, which contains all the essential operations, so we'll install that first. Next, we'll also pick up `generator-hyperledger-composer`, `composer-rest-server` and `Yeoman` plus the `generator-hyperledger-composer`. Those last 3 are not core parts of the development environment, but they'll be useful if you're following the tutorials or developing applications that interact with your Business Network, so we'll get them installed now.

1. Essential CLI tools:

npm install -g composer-cli@next
npm install -g composer-cli

2. Utility for running a REST Server on your machine to expose your business networks as RESTful APIs:

npm install -g composer-rest-server@next
npm install -g composer-rest-server

3. Useful utility for generating application assets:

npm install -g generator-hyperledger-composer@next
npm install -g generator-hyperledger-composer

4. Yeoman is a tool for generating applications, which utilises `generator-hyperledger-composer`:

Expand All @@ -49,7 +48,7 @@ If you've already tried {{site.data.conrefs.composer_short}} online, you'll have

5. Browser app for simple editing and testing Business Networks:

npm install -g composer-playground@next
npm install -g composer-playground

### Step 3: Set up your IDE
Whilst the browser app _can_ be used to work on your Business Network code, most users will prefer to work in an IDE. Our favourite is `VSCode`, because a {{site.data.conrefs.composer_short}} extension is available.
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -40,7 +40,7 @@ In order to deploy the REST server as a Docker container with additional LoopBac

Here is an example Dockerfile that adds the LoopBack connector for MongoDB and the Passport strategy for GitHub to the Docker image:

FROM hyperledger/composer-rest-server:next
FROM hyperledger/composer-rest-server
RUN npm install --production loopback-connector-mongodb passport-github && \
npm cache clean --force && \
ln -s node_modules .node_modules
Expand Down Expand Up @@ -76,7 +76,7 @@ The examples are based on the business network that is deployed to {{site.data.c
3. Extend the Docker image for the REST server by adding the LoopBack connector for MongoDB and the Passport strategy for GitHub authentication. Create a new, empty directory on your local file system, and create a new file named `Dockerfile` in the new directory, with the following contents:
```
FROM hyperledger/composer-rest-server:next
FROM hyperledger/composer-rest-server
RUN npm install --production loopback-connector-mongodb passport-github && \
npm cache clean --force && \
ln -s node_modules .node_modules
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -22,9 +22,9 @@ After deploying {{site.data.conrefs.composer_full}} you may wish to update to a

2. Install the latest version of the {{site.data.conrefs.composer_full}} components by using the following commands:

npm install -g composer-cli@next
npm install -g composer-rest-server@next
npm install -g generator-hyperledger-composer@next
npm install -g composer-cli
npm install -g composer-rest-server
npm install -g generator-hyperledger-composer


## What next?
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -53,7 +53,7 @@ As mentioned, we will store credentials in a persistent data store once the appr
2. In the temporary directory, create a docker file called `Dockerfile` in an editor and paste into the following sequence (including special backslash `\` characters below needed after the `RUN` and `npm` lines below - ie the continuation character ):

```
FROM hyperledger/composer-rest-server:next
FROM hyperledger/composer-rest-server
RUN npm install --production loopback-connector-mongodb passport-google-oauth2 && \
npm cache clean --force && \
Expand All @@ -76,7 +76,7 @@ You should see output similar to the following with the bottom 2 lines indicatin

docker build -t myorg/composer-rest-server .
Sending build context to Docker daemon 4.203GB
Step 1/2 : FROM hyperledger/composer-rest-server:next
Step 1/2 : FROM hyperledger/composer-rest-server
---> e682b4374837
Step 2/2 : RUN npm install --production loopback-connector-mongodb passport-google-oauth2 && npm cache clean --force && ln -s node_modules .node_modules
---> Running in 7a116240be21
Expand Down

0 comments on commit c7e94a6

Please sign in to comment.