Quick Start Guide¶
Get Studio Platform running in minutes with this comprehensive quick start guide.
🚀 Prerequisites¶
System Requirements¶
| Requirement | Minimum | Recommended |
|---|---|---|
| CPU | 4 cores | 8 cores |
| Memory | 8 GB RAM | 16 GB RAM |
| Storage | 50 GB free | 100 GB free |
| Docker | 20.10+ | Latest |
| Docker Compose | 2.0+ | Latest |
Software Dependencies¶
- Docker Desktop (Windows/Mac) or Docker Engine (Linux)
- Git for cloning the repository
- Text editor for configuration (VS Code recommended)
📋 Step-by-Step Installation¶
Step 1: Clone the Repository¶
Step 2: Configure Environment¶
Edit the .env file with your preferred text editor:
Step 3: Essential Environment Variables¶
These are the minimum required variables to get Studio running:
# Database Configuration
POSTGRES_USER=studio_user
POSTGRES_PASSWORD=your_secure_password_here
POSTGRES_DB=auditdb
# Security Secrets (Generate strong random strings)
JWT_SECRET=your_jwt_secret_here_32_chars_min
MINIO_SECRET_KEY=your_minio_secret_here_32_chars_min
# Neo4j Configuration
NEO4J_AUTH=neo4j/your_neo4j_password_here
# Fleet Database
FLEET_MYSQL_PASSWORD=your_fleet_mysql_password_here
# AI Configuration (Optional but recommended)
GOOGLE_API_KEY=your_google_api_key_here
Security Note
The application will not start if critical security secrets are missing. Use strong, unique passwords for all secrets.
Generating Secrets
Use these commands to generate secure secrets:
Step 4: Start the Platform¶
Step 5: Verify Installation¶
# Check service status
docker-compose ps
# Run health verification
docker-compose exec backend node live-verification/live-all.js
🌐 Accessing Studio¶
Once the services are running, you can access Studio at:
| Service | URL | Description |
|---|---|---|
| Main Application | http://localhost | Studio Platform |
| Fleet Console | http://localhost:8080 | Device Management |
| Grafana | http://localhost:3002 | Monitoring Dashboard |
| MinIO Console | http://localhost:9001 | Object Storage |
Default Login Credentials¶
| Role | Password | |
|---|---|---|
| Admin | admin@example.com | admin123# |
| Manager | manager@example.com | manager123# |
| Customer | customer@example.com | customer123# |
Security Warning
Change default passwords immediately after first login for production deployments.
✅ Verification Checklist¶
Service Health Check¶
# Check all services are running
docker-compose ps
# Expected output should show "healthy" status for:
# - postgres
# - backend
# - frontend
# - kong
# - kratos
# - redis
# - neo4j
# - minio
Platform Functionality Test¶
- Login to the main application
- Create a new project with a compliance framework
- Upload a sample evidence file
- Test the AI assistant with a compliance question
- View the risk dashboard
API Health Check¶
# Test backend API
curl http://localhost/api/health
# Test frontend
curl http://localhost/
# Expected: HTTP 200 OK responses
🔧 Common Setup Issues¶
Port Conflicts¶
If you encounter port conflicts, modify the docker-compose.yml:
Permission Issues¶
On Linux, you might need to adjust Docker permissions:
# Add user to docker group
sudo usermod -aG docker $USER
# Restart Docker service
sudo systemctl restart docker
Memory Issues¶
If services fail to start due to memory constraints:
- Increase Docker memory allocation in Docker Desktop settings
- Or reduce resource limits in
docker-compose.yml:
# Example: Reduce backend memory limits
backend:
deploy:
resources:
limits:
memory: 1G # Reduced from 2G
Network Issues¶
If services can't communicate:
# Reset Docker networks
docker network prune
# Restart services
docker-compose down
docker-compose up -d
🏗️ Production Considerations¶
Security Enhancements¶
For production deployment, implement these security measures:
-
SSL/TLS Certificates
-
Environment Variables
-
Network Security
- Use firewall rules
- Implement VPN access
- Configure intrusion detection
Performance Optimization¶
-
Resource Allocation
-
Database Optimization
- Configure connection pooling
- Enable query caching
- Set up read replicas
Backup Strategy¶
# Set up automated backups
./scripts/backup-setup.sh
# Manual backup
docker-compose exec postgres pg_dump -U studio_user auditdb > backup.sql
📚 Next Steps¶
Explore Features¶
- User Guide - Learn about all platform features
- Admin Guide - Configure system settings
- Developer Guide - Explore APIs and integrations
Integrations¶
- FleetDM Integration - Set up device management
- Prowler Integration - Configure cloud scanning
- n8n Workflows - Create automation workflows
Advanced Configuration¶
- SSL/TLS Setup - Enable HTTPS
- Monitoring Setup - Configure observability
- Backup & Recovery - Set up data protection
🆘 Getting Help¶
Troubleshooting¶
- Common Issues - Solutions to frequent problems
- Performance Issues - Optimization guides
- Security Issues - Security troubleshooting
Community Support¶
- GitHub Issues - Report bugs and request features
- Documentation - Browse comprehensive guides
- Community Forums - Connect with other users
Enterprise Support¶
For enterprise customers: - Priority Support - 24/7 assistance - Dedicated Account Manager - Personalized guidance - Custom Training - Team onboarding sessions
Congratulations! 🎉
You now have Studio Platform running! Take some time to explore the features and check out our detailed guides for advanced configuration and usage.
Bookmark This Guide
Save this page for future reference. You'll need it when setting up additional environments or troubleshooting issues.