Files
nofx/docs/getting-started/README.md
zbhan 2351bb95c3 Feat: Update docs
- 重构文档结构
- 更新文档内容
- 制定roadmap
- 提供中/EN 双语文档
2025-11-01 15:05:24 -04:00

2.8 KiB

🚀 Getting Started with NOFX

Language: English | 中文

This section contains all the documentation you need to get NOFX up and running.

📋 Deployment Options

Choose the method that best fits your needs:

Best for: Beginners, quick setup, production deployments

Pros:

  • One-command setup
  • All dependencies included
  • Easy to update and manage
  • Isolated environment

Quick Start:

cp config.example.jsonc config.json
./start.sh start --build

🔧 PM2 Deployment

Best for: Advanced users, development, custom setups

Pros:

  • Direct process control
  • Better for development
  • Lower resource usage
  • More flexible

Quick Start:

go build -o nofx
cd web && npm install && npm run build
pm2 start ecosystem.config.js

🤖 AI Configuration

Custom AI Providers

Use custom AI models or third-party OpenAI-compatible APIs:

  • Custom DeepSeek endpoints
  • Self-hosted models
  • Other LLM providers

🔑 Prerequisites

Before starting, ensure you have:

For Docker Method:

  • Docker 20.10+
  • Docker Compose V2

For Manual Method:

  • Go 1.21+
  • Node.js 18+
  • TA-Lib library
  • PM2 (optional)

📚 Next Steps

After deployment:

  1. Configure AI Models → Web interface at http://localhost:3000
  2. Set Up Exchange → Add Binance/Hyperliquid credentials
  3. Create Traders → Combine AI models with exchanges
  4. Start Trading → Monitor performance in dashboard

⚠️ Important Notes

Before Trading:

  • ⚠️ Test on testnet first
  • ⚠️ Start with small amounts
  • ⚠️ Understand the risks
  • ⚠️ Read Security Policy

API Keys:

  • 🔑 Never commit API keys to git
  • 🔑 Use environment variables
  • 🔑 Restrict IP access
  • 🔑 Enable 2FA on exchanges

🆘 Troubleshooting

Common Issues:

  1. Docker build fails → Check Docker version, update to 20.10+
  2. TA-Lib not foundbrew install ta-lib (macOS) or apt-get install libta-lib0-dev (Ubuntu)
  3. Port 8080 in use → Change API_PORT in .env file
  4. Frontend won't connect → Check backend is running on port 8080

Need more help?


← Back to Documentation Home