Sean Zellmer b11bb658c7 Add Best practices article (#186) ...

* Add aside about using only one corestore instance per application

A single corestore instance covers all needs and avoids pitfalls (such
as file locks and named hypercores not being the same key) that come
from multiple corestore instances.

* Add note for best practice to create one hyperswarm instance per app

* Create a best practices guide for Pear Application development

* Add "Best Practices" article to SUMMARY.md & README.md

* Include points added to the guides on using single swarm & store

* Fix capitalization in Best Practices article

2025-05-31 01:01:23 -05:00

..

connect-to-many-peers-by-topic-with-hyperswarm.md

Add Best practices article (#186)

2025-05-31 01:01:23 -05:00

connect-two-peers-by-key-with-hyperdht.md

Clarify where to run apps in howtos (#170)

2025-02-28 12:16:09 +01:00

create-a-full-peer-to-peer-filesystem-with-hyperdrive.md

Remove findingPeers() & some flush() flow from hyperswarm examples (#176)

2025-04-10 19:15:57 +02:00

replicate-and-persist-with-hypercore.md

Remove findingPeers() & some flush() flow from hyperswarm examples (#176)

2025-04-10 19:15:57 +02:00

share-append-only-databases-with-hyperbee.md

Remove findingPeers() & some flush() flow from hyperswarm examples (#176)

2025-04-10 19:15:57 +02:00

work-with-many-hypercores-using-corestore.md

Add Best practices article (#186)

2025-05-31 01:01:23 -05:00