Merge pull request #9 from Premian-Labs/dk/update-readme

feat: Add automated deployment and update docs

Author: syphrpunk

CLAUDE.md

@@ -8,17 +8,29 @@
 - View logs: `docker-compose logs -f`
 - Stop services: `docker-compose down`
 
+## Automated Deployment
+- GitHub Actions automatically deploy to Railway on pushes to:
+  - `dev` branch: Deploys to development environment
+  - `main` branch: Deploys to production environment
+- Both the eRPC server and monitoring stack are deployed separately using distinct Railway service IDs
+
 ## Environment Variables
 - Required: `REDIS_ADDR`, `REDIS_PASSWORD`, `RPC_API_SECRET`
 - Optional: Various API keys for RPC providers (ALCHEMY_API_KEY, INFURA_API_KEY, etc.)
+- GitHub Actions secrets needed:
+  - `RAILWAY_TOKEN`: Authentication token for Railway
+  - `SVC_ID_ERPC`: Railway service ID for eRPC server
+  - `SVC_ID_MONITOR`: Railway service ID for monitoring stack
 
 ## Container Structure
 - eRPC server: Handles RPC requests, runs on port 4000
   - Healthcheck: JSON-RPC `net_version` request to port 4000
+  - Uses `Dockerfile.erpc` and `railway.erpc.json` for configuration
 - Metrics endpoint: Port 4001
 - Monitoring stack: 
   - Grafana (port 3000) with healthcheck at /api/health
   - Prometheus (port 9090)
+  - Uses `Dockerfile.monitoring` and `railway.monitor.json` for configuration
 
 ## Code Style Guidelines
 - Configuration files use YAML format

README.md

@@ -8,7 +8,15 @@
 
 [![Deploy on Railway](https://railway.app/button.svg)](https://railway.app/template/10iW1q)
 
-# License
+## Deployment
+
+This repository is configured with GitHub Actions workflows that automatically deploy:
+- The eRPC server and monitoring stack to the development environment when code is pushed to the `dev` branch
+- The eRPC server and monitoring stack to the production environment when code is pushed to the `main` branch
+
+The deployment uses Railway's service IDs to deploy the eRPC server and monitoring stack separately.
+
+## License
 
 Apache 2.0