FAQ
Common questions about installation, operation, identity, and usage.
Node Operator Docs
Common questions about installation, operation, identity, and usage.
git --versioncurl -fsSL https://epress.world/install.sh | bash -xFor curl installs, edit the environment configuration:
cd ~/epress
echo "PORT=8545" >> .env.local
npm run stop && npm run startFor Docker, adjust the -p mapping: -p 8545:8543
Back up this directory regularly to preserve your content.
docker cp my-epress-node:/app/data ./backupYour wallet provides cryptographic identity that works across all epress nodes:
Yes. epress supports any wallet that implements WalletConnect or browser wallet injection:
No. Connecting your wallet and signing content are off-chain operations. You only sign messages, not blockchain transactions. No ETH is spent.
Yes, your address is public and serves as your identity. However, your private key and seed phrase never leave your device. They are only used to sign messages locally.
Your identity is tied to your wallet address. To use a different address, you would need to re-establish follow relationships from the new address. Your content remains on your node regardless of wallet.
Your timeline shows signed content from nodes you follow. If empty:
Yes, you can delete content from your node. However, content that has been replicated to other nodes may persist there. Signed content includes timestamps, so deleted content cannot be republished with the same signature.
Every signed publication includes:
Other nodes verify this signature before accepting content. Without the private key, content cannot be forged.
Currently, epress focuses on public content. Private messaging is not yet implemented but may be added in future versions.
cd ~/epress && npm run statusdocker ps to confirm container is runningdocker logs -f my-epress-nodeCurl install:
cd ~/epress && npm run stop && npm run startDocker:
docker stop my-epress-node
docker start my-epress-nodeCurl install:
cd ~/epress && git pull && npm install && npm run build && npm run stop && npm run startDocker:
docker pull ghcr.io/epressworld/epress
docker stop my-epress-node
docker rm my-epress-node
docker run -d -p 8543:8543 -p 8544:8544 -v epress-data:/app/data --name my-epress-node ghcr.io/epressworld/epressYes. Adjust the port mappings or environment variables. Keep internal ports unchanged and only modify the host-side ports.