You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 8, 2020. It is now read-only.
Copy file name to clipboardExpand all lines: packages/composer-website/jekylldocs/business-network/cloud-wallets.md
+8-11Lines changed: 8 additions & 11 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -21,13 +21,8 @@ Whenever a `BusinessNetworkConnection` or `AdminConnection` is made, it has an a
21
21
22
22
Custom implementations can be written for any given backend database or object store, enabling the specification of a `CardStore` that is in a non-default file location, a separate docker container, or hosted in a cloud based data store. The store configuration can be completed using either a configuration file, or by using environment variables.
23
23
24
-
-[composer-tools/composer-wallet-redis](https://github.com/hyperledger/composer-tools/tree/master/packages/composer-wallet-redis) - provides a backing store using a Redis server
25
-
-[@ampretia/composer-wallet-ibmcos](https://github.com/ampretia/composer-wallet-ibmcos) - provides a backing store using the IBM Cloud Object Store. This has an S3 compatible API
26
-
27
24
Multiple cloud wallet implementations can be installed using global npm installs.
28
25
29
-
For more details of the writing a new cloud wallet implementation, see the following [README](https://github.com/hyperledger/composer-tools/tree/master/packages/composer-wallet-redis).
30
-
31
26
# Configuring a custom wallet
32
27
33
28
There are two ways to define the configuration for a custom wallet: by using a `.json` configuration file, or by defining environment variables.
@@ -39,7 +34,7 @@ There are two ways to define the configuration for a custom wallet: by using a `
39
34
For production deployments, it is more useful to be able to configure the card store outside of the application,
40
35
{{site.data.conrefs.composer_full}} uses the standard configuration module `config`. The configuration file is loaded from a sub-directory of the current working directory called `config`. The default configuration file is called `default.json`, the configuration file name can be changed using the `NODE_ENV` environment variable.
41
36
42
-
The following configuration file uses the Redis format as an example:
37
+
For example here is a configuration for a cloud wallet implementation called `composer-wallet-redis`
43
38
44
39
```
45
40
{
@@ -94,14 +89,13 @@ The same `.json` snippet may be exported as an environment variable.
94
89
95
90
The following GitHub repositories contain implementations of cloud custom wallets using Redis and the IBM Cloud Object Store, respectively.
96
91
97
-
-[composer-tools/composer-wallet-redis](https://github.com/ampretia/composer-wallet-redis) - provides a backing store using a Redis server
98
-
-[@ampretia/composer-wallet-ibmcos](https://github.com/ampretia/composer-wallet-ibmcos) - provides a backing store using the IBM Cloud Object Store. This has an S3 compatible API.
92
+
-[composer-tools/composer-wallet-redis](https://github.com/hyperledger/composer-tools/tree/master/packages/composer-wallet-redis) - provides a backing store using a Redis server
93
+
-[composer-tools/composer-wallet-ibmcos](https://github.com/hyperledger/composer-tools/tree/master/packages/composer-wallet-ibmcos) - provides a backing store using the IBM Cloud Object Store. This has an S3 compatible API
94
+
-[composer-tools/composer-wallet-cloudant](https://github.com/hyperledger/composer-tools/tree/master/packages/composer-wallet-cloudant) - provides a backing store using the IBM Cloudant
99
95
100
96
Multiple cloud custom wallet implementations can be installed using global npm installs.
101
97
102
-
For more details of the writing a new cloud based custom wallet implementation, see the following [README](https://github.com/hyperledger/composer-tools/tree/master/packages/composer-wallet-redis).
103
-
104
-
To migrate to either the Redis or IBM Cloud Object Store cloud custom wallet solutions, refer to the README files of the relevant GitHub repository.
98
+
To migrate to these custom wallet solutions, refer to the README files of the relevant GitHub repository.
105
99
106
100
In a general sense, migrating to a cloud wallet implementation has three steps.
107
101
@@ -167,3 +161,6 @@ This has now changed and Card stores must now be specified differently:
# Cloud Wallets and Hyperledger Composer Rest Server
165
+
166
+
For convenience, the latest Hyperledger Composer Rest Server docker image will have all the cloud wallets available on the github repository for composer-tools preloaded into the image.
0 commit comments