* Add `bare-expo` to "Bare on Mobile" w/ brief Pear-end explanation
* Add footnote about the term worklet to Bare on Mobile
* Add phrase about using RPC to communicate w/ worklet in Bare on Mobile
* Reword note about `bare-ios` & `bare-android` examples
* Remove `--` for app option passthrough
Changed since `paparam` was used for parsing command line options:
85892a6a32a84ae42a548f8e3ac0b5dbedd70c80
Now uses `cmd.rest` for app args.
* Use `Pear.config.args` for howto scripts
* Update "starting a pear desktop project" guide to match template
* Remove `--no-ask-trust` flag from `pear run` cli doc
This command was replaced by `--no-ask` which was already in the
documentation. Updated a reference to `--no-ask-trust` in the 'Sharing a
Pear Application' guide.
* Fix typos in "Releasing a Pear Application" guide
* Correct application storage folder name in hyperbee howto
* Add missing `test/index.test.js` in project structure for terminal guide
* Remove language about app continuing to run
This is no longer true at least as of pear:
v0.5114.pqbzjhqyonxprx8hghxexnmctw75mr91ewqw5dxe1zmntfyaddqy / v1.5.0
* Fix extra indention in example code for hypercore howto
* Format json in `_template.json` example
* Add instructions to set up a minimal `package.json` for testing template
Without this, the next step of `pear run --dev .` does not work since
`pear` expects a `package.json` file.
* Rename hyperbee reader app in hyperdrive howto to avoid name conflict
Naming only matters if someone is following the guides and starts each
guide from the same root directory. If they do, then `bee-reader-app`
from the hyperdrive conflicts with the `bee-reader-app` from the
hyperbee howto.
* Remove unrelated youtube tutorial from hyperswarm howto
* Update guide/creating-a-pear-init-template.md
Co-authored-by: David Mark Clements <huperekchunow@googlemail.com>
* Fix spelling mistake
Co-authored-by: David Mark Clements <huperekchunow@googlemail.com>
---------
Co-authored-by: David Mark Clements <huperekchunow@googlemail.com>
* Change `key` to `link` to match CLI functionality
CLI commands have changed to take the link format (`pear://<key>`)
instead of the key.
* Update guides to use `link` instead of `key` for CLI commands
Servers can be run on normal home computers, as the DHT will UDP holepunch connections are personal to users.
-->
"You can run servers on normal home computers, as the DHT will UDP holepunch connections for you."
Added explicit `.` for the first run of the app to make it more obvious
that the second run of the app is just passing the topic instead of
automatically generating one.