mirror of
https://github.com/aljazceru/pear-docs.git
synced 2025-12-18 06:54:22 +01:00
b11bb658c7
* 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
2.8 KiB
2.8 KiB
Table of contents
Pear runtime
- Command-Line-Interface (CLI)
- Application-Programming-Interface (API)
- Application Configuration
- Troubleshooting Applications
- Frequently Asked Questions
Bare reference
- Overview
- Application-Programming-Interface (API)
- Node.js Compatibility with Bare
- Bare Modules
- Troubleshooting with Bare
Guides
- Getting Started
- Starting a Pear Desktop Project
- Making a Pear Desktop Application
- Starting a Pear Terminal Project
- Making a Pear Terminal Application
- Sharing a Pear Application
- Marking a Release
- Making a Bare Mobile Application
- Debugging a Pear Terminal Application
- Creating a Pear Init Template
- Best Practices
Building blocks
How-tos
- Connect two peers
- Connect many peers
- Replicate & persist
- Manage multiple Hypercores
- Share append-only databases
- Create a p2p filesystem