Server-Side Installation Overview
Ridy can be installed using two primary methods, depending on your needs and expertise:
| Method | Recommended For | Setup Time | System Requirements | Flexibility |
|---|---|---|---|---|
| Docker Mode (Pre-built) | Fast setup, consistent environments | ⭐ Quick | Clean Linux OS | 🔒 Less customizable |
| Source Code (Docker Compose) | Developers needing customization + containerization | ⏱️ Moderate | Docker, source code access | 🛠️ High control + containers |
| Dev Mode (Manual) | Advanced development, debugging | ⏱️ Moderate | Node.js, MySQL, Redis, NX | 🛠️ Full control |
When to Use What
Use Docker Mode (Pre-built) if you want:
- The quickest, most consistent setup
- Minimal manual configuration
- A stable base to evaluate or deploy in staging
- No need to modify backend code
Use Source Code Installation if you:
- Want to build from source but keep containerization benefits
- Plan to customize backend services
- Need reproducible deployments with code modifications
- Prefer Docker for consistency while maintaining full code access
Use Dev Mode (Manual) if you:
- Need deep debugging capabilities
- Want direct access to running processes
- Are developing new features or integrations
- Prefer running services natively without Docker
📝 Need help deciding? Start with Docker Mode for evaluation, use Source Code installation for customized production deployments, and switch to Dev Mode for active development.
Continue to: