This AlphaBeta808 Trading Bot is optimized for deployment on Railway platform with automatic configuration.
- Click the "Deploy on Railway" button above
- Connect your GitHub account
- Set your environment variables (see below)
- Deploy automatically!
Set these in your Railway dashboard before deployment:
SECRET_KEY=your-secret-key-32-chars # Generate with: openssl rand -base64 32
WEB_ADMIN_USER=admin # Change this!
WEB_ADMIN_PASSWORD=secure-password-here # Change this!
WEBHOOK_SECRET=webhook-secret-32-chars # Generate with: openssl rand -base64 32BINANCE_API_KEY=your-binance-api-key
BINANCE_API_SECRET=your-binance-api-secretFLASK_ENV=production
LOG_LEVEL=INFO
EMAIL_ENABLED=false
TELEGRAM_ENABLED=false- ✅ Automatic Health Checks: Railway monitors
/healthendpoint - ✅ Zero-Downtime Deployments: Seamless updates
- ✅ Built-in Monitoring: CPU, memory, and network metrics
- ✅ Persistent Storage: SQLite database persistence
- ✅ Environment Management: Secure variable storage
- ✅ Custom Domains: Connect your own domain
- ✅ SSL/TLS: Automatic HTTPS certificates
Your app will be available at: https://your-app-name.railway.app
Check health: https://your-app-name.railway.app/health
Expected response:
{
"status": "healthy",
"timestamp": "2025-05-27T...",
"version": "1.0.0"
}- Go to your Railway app URL
- Login with your configured credentials
- Configure your trading parameters
- Navigate to Settings → API Configuration
- Test your Binance API connection
- Enable trading mode (start with paper trading!)
Railway deployment uses these optimized files:
railway.toml: Railway platform configurationDockerfile.railway: Optimized Docker build for RailwayProcfile: Service startup configuration.env.railway: Environment variables template
- Logs: Real-time application logs
- Metrics: CPU, memory, network usage
- Deployments: Deployment history and rollbacks
- Performance: Real-time P&L and statistics
- Positions: Active trades and portfolio
- Signals: ML model predictions and signals
- Change Default Credentials: Update admin username/password
- Use Testnet First: Test with Binance sandbox before live trading
- Monitor API Usage: Keep track of API calls and limits
- Regular Backups: Export configurations regularly
- Key Rotation: Rotate API keys periodically
- Check build logs in Railway dashboard
- Verify all required environment variables are set
- Ensure your GitHub repository is public or properly connected
- Verify
/healthendpoint is accessible - Check application logs for startup errors
- Ensure PORT environment variable is set correctly
- Verify your app URL is correct
- Check admin credentials in environment variables
- Look for authentication errors in logs
Using Railway CLI:
# Install CLI
npm install -g @railway/cli
# Login and link
railway login
railway link
# View logs
railway logs
# Check status
railway status
# Update environment
railway variables set SECRET_KEY=new-secretRailway automatically redeploys when you push to your connected GitHub repository.
- Go to Railway dashboard
- Click "Deploy" → "Redeploy"
- Monitor deployment logs
Update variables in Railway dashboard → Variables section
- Hobby Plan: $5/month for personal projects
- Pro Plan: $20/month for production use
- Usage-based: Pay for what you use (CPU, memory, network)
See Railway Pricing for current rates.
- Click "Deploy on Railway" button
- Connect GitHub repository
- Set
SECRET_KEYenvironment variable - Set
WEB_ADMIN_USERandWEB_ADMIN_PASSWORD - Set
BINANCE_API_KEYandBINANCE_API_SECRET - Deploy and wait for health check to pass
- Access dashboard and configure trading
- Start with paper trading mode
- Monitor performance and logs
🚀 Ready to deploy? Click here to deploy on Railway