- Add SYNC_GUIDE.md: Complete guide for keeping code synchronized - Git workflow best practices - How to handle merge conflicts - Security guidelines (no secrets in code) - Multi-machine synchronization - Add QUICK_REFERENCE.md: One-page cheat sheet - Essential commands for daily work - Common troubleshooting - Secrets management - Links to full documentation - Add deploy/sync-dev.sh: Automated sync script - Interactive fetch and merge - Shows diffs before merging - Detects merge conflicts - Updates from branch: claude/hostinger-remote-deployment-TGVof - Update Makefile with 'make sync-dev' target Usage: make sync-dev # Auto-sync with dev branch make setup-telegram # Setup Telegram bot make setup-tailscale # Setup Tailscale security make build && make run # Test locally Documentation structure: QUICK_REFERENCE.md ← Start here (1 page) SETUP_COMPLETE.md ← Setup guide (detailed) SYNC_GUIDE.md ← Git & sync guide TELEGRAM_QUICKSTART.md ← Telegram in 3 steps docs/TELEGRAM_SETUP.md ← Full Telegram reference https://claude.ai/code/session_019vXaqxGmkdCjM8m3jp6rYj
3.2 KiB
3.2 KiB
⚡ PicoClaw Quick Reference
🚀 Setup (One-Time Only)
# 1. Secure VPS with Tailscale
make setup-tailscale
# 2. Configure Telegram Bot
make setup-telegram
# Done! 🎉
🔄 Daily Updates
# Sync with latest code
make sync-dev
# Check status
git status
🐛 Common Commands
# Build locally
make build
# Run locally (development)
make run
# Run tests
make test
# Check code quality
make check
# View logs on server
ssh root@YOUR_IP 'docker compose logs picoclaw | tail -50'
# Restart bot (if needed)
ssh root@YOUR_IP 'docker compose restart picoclaw'
📁 Important Files
picoclaw/
├── deploy/hostinger/
│ ├── setup-telegram.sh ← Run: make setup-telegram
│ ├── setup-tailscale.sh ← Run: make setup-tailscale
│ ├── setup-server.sh ← Runs on VPS initial setup
│ └── docker-compose.production.yml
├── .github/workflows/
│ └── deploy-hostinger.yml ← Auto-deploys on git push
├── config/
│ ├── config.json ← Edit on VPS (nano)
│ └── .env ← Edit on VPS (nano)
└── docs/
└── TELEGRAM_SETUP.md ← Full guide with troubleshooting
🔐 Secrets Management
# Add/update GitHub Secret
gh secret set PICOCLAW_TELEGRAM_BOT_TOKEN -b "YOUR_TOKEN"
# List secrets (values hidden)
gh secret list
# Secrets used in deploy:
# - PICOCLAW_TELEGRAM_BOT_TOKEN
# - ANTHROPIC_API_KEY
# - HOSTINGER_HOST
# - HOSTINGER_SSH_USER
# - HOSTINGER_SSH_PASSWORD
# - HOSTINGER_SSH_PORT
📱 Telegram Bot
# Create bot: https://t.me/botfather
# Commands: /start, /help, /show, /list
# Get your Telegram user ID (check logs):
ssh root@YOUR_IP 'docker compose logs picoclaw | grep user_id'
# Add to whitelist (config/config.json):
"allow_from": ["123456789", "987654321"]
🔗 Tailscale
# Get your Tailnet IP
ssh root@YOUR_IP 'tailscale ip -4'
# Access via Tailnet
http://100.x.x.x:18790
# Or via hostname
https://picoclaw.YOUR-TAILNET.ts.net
🚨 If Something Breaks
# 1. Check logs
ssh root@YOUR_IP 'docker compose logs --tail=100 picoclaw'
# 2. Restart container
ssh root@YOUR_IP 'docker compose restart picoclaw'
# 3. Check if port is open
ssh root@YOUR_IP 'netstat -tuln | grep 18790'
# 4. Verify GitHub Secrets are set
gh secret list
# 5. Force redeploy
git commit --allow-empty -m "chore: trigger redeploy"
git push origin claude/hostinger-remote-deployment-TGVof
📚 Full Guides
- Setup Complete Guide: SETUP_COMPLETE.md
- Sync & Git Guide: SYNC_GUIDE.md
- Telegram Setup: docs/TELEGRAM_SETUP.md
- Telegram Quickstart: TELEGRAM_QUICKSTART.md
💡 Tips
- Always
make sync-devbefore starting work - Use
make checkto verify code before pushing - GitHub Actions deploys automatically on push
- Keep bot token in GitHub Secrets, never in code
- Test locally with
make build && make runfirst
Need help? Check the full guides or open an issue! 🚀