Clarify where to run apps in howtos (#170)

* Add missing argument for `drive-writer-app` key in p2p fs howto

* Clarify where applications should be run in howtos

The wording is adjusted to make it clearer when one pear app should be
left running and where to run apps in general. In some cases a reader
would be prompted to make a directory and then change directories into
it and modify some files. After modifying the files, they would be asked
to change into the directory again even though they would be in the
directory already. This has been clarified by removing commands for
changing directory where the reader will be already in that directory.
This commit is contained in:
Sean Zellmer
2025-02-28 05:16:09 -06:00
committed by GitHub
parent b011d81d27
commit c8b7455f25
3 changed files with 7 additions and 14 deletions

View File

@@ -73,14 +73,13 @@ if (core.length <= 1) {
}
```
Open the app with `pear run --dev .`:
Run the app with:
```
cd bee-writer-app
pear run --dev .
```
Start the `bee-reader-app` project with the following commands:
Start the `bee-reader-app` project in a new terminal with the following commands:
```
mkdir bee-reader-app
@@ -148,7 +147,6 @@ stdin.on('data', (data) => {
Open the `bee-reader-app` and pass it the core key:
```
cd bee-reader-app
pear run --dev . <SUPPLY KEY HERE>
```
@@ -213,7 +211,6 @@ console.log(`Decoded Block ${seq}`, Node.decode(lastBlock))
Open the `core-reader-app` with `pear run --dev .`, passing the core key to it:
```
cd core-reader-app
pear run --dev . <SUPPLY KEY HERE>
```