Welcome
Getting Started
How to Guides
Application vs Blocklet
Create Blocklet
Compose Blocklets
Develop Blocklet
User and Passport
Communicate with DID Wallet
Blocklet Storage
Using Blocklet Preferences
Using Blocklet Logger
Add PWA Integration to Blocklet
Build blocklet for profit [deprecated]
Bundle your blocklet
Manage Blocklet Versions
Publish your blocklet to the world
Deploy your blocklet
Read/Write blockchain in blocklet
Operation your blocklet
Reference Guides
DID Connect
blocklet.yml
blocklet.js
Blocklet SDK (Node.js)
Blocklet SDK (Browser)
Blocklet Service
Blocklet CLI
Blocklet Server CLI
Blocklet UI
Blocklet GitHub Actions
Blocklet Studio
Blocklet Manager
Security
Performance
Developer Best Practices.
Known Issues or Limitations
Setup Blocklet Server
WebHooks
OAuth Server
Access Key
MCP Servers
Conceptual Guides
Frequently Asked Questions
When stuck in maintenance mode?
Blocklet server supports several maintenance operations directly from the server dashboard:
- upgrading itself to a new version, either production or beta release
- restarting the server if the server processes consumes too much resources such as memory
Due to the current distribution method, we are using npm, some exceptions may happen when doing an upgrade from the server dashboard.
If you are stuck in maintenance mode, here is a fallback way to escape and recover your server:
npm install -g @blocklet/cli@beta // please use version v1.16.21-beta-445a8baa and above
blocklet server cleanup --target maintenance-status // cleanup the maintenance status in server state db
blocklet server start