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
Copy file name to clipboardExpand all lines: motoko/pub-sub/README.md
+9-43Lines changed: 9 additions & 43 deletions
Original file line number
Diff line number
Diff line change
@@ -4,58 +4,24 @@ This sample project demonstrates how functions may be passed as arguments of int
4
4
5
5
A common problem in both distributed and decentralized systems is keeping separate services (or canisters) synchronized with one another. While there are many potential solutions to this problem, a popular one is the publisher/subscriber pattern or "PubSub". PubSub is an especially valuable pattern on the Internet Computer as its primary drawback, message delivery failures, does not apply.
6
6
7
-
## Prerequisites
8
-
This example requires an installation of:
7
+
## Deploying from ICP Ninja
9
8
10
-
-[x] Install the [IC SDK](https://internetcomputer.org/docs/current/developer-docs/setup/install/index.mdx).
11
-
-[x] Clone the example dapp project: `git clone https://github.com/dfinity/examples`
### 1. [Download and install the IC SDK.](https://internetcomputer.org/docs/building-apps/getting-started/install)
16
14
17
-
Navigate into the folder containing the project's files and start a local instance of the Internet Computer with the commands:
15
+
### 2. Download your project from ICP Ninja using the 'Download files' button on the upper left corner, or [clone the GitHub examples repository.](https://github.com/dfinity/examples/)
18
16
19
-
```bash
20
-
cd examples/motoko/pub-sub
21
-
dfx start --background
22
-
```
17
+
### 3. Navigate into the project's directory.
23
18
24
-
##Step 2: Deploy the canisters:
19
+
### 4. Deploy the project to your local environment:
If you base your application on this example, we recommend you familiarize yourself with and adhere to the [security best practices](https://internetcomputer.org/docs/current/references/security/) for developing on the Internet Computer. This example may not implement all the best practices.
57
-
58
-
For example, the following aspects are particularly relevant for this app, since it makes inter-canister calls:
59
-
*[Be aware that state may change during inter-canister calls.](https://internetcomputer.org/docs/current/developer-docs/security/security-best-practices/overview)
60
-
*[Only make inter-canister calls to trustworthy canisters.](https://internetcomputer.org/docs/current/developer-docs/security/security-best-practices/overview)
61
-
*[Don’t panic after await and don’t lock shared resources across await boundaries.](https://internetcomputer.org/docs/current/developer-docs/security/security-best-practices/overview)
27
+
If you base your application on this example, it is recommended that you familiarize yourself with and adhere to the [security best practices](https://internetcomputer.org/docs/building-apps/security/overview) for developing on ICP. This example may not implement all the best practices.
0 commit comments