Looks Like This Service Is On Hold
I will build a custom cicd orchestrator for railway cloud and docker
Pakistan
About this Gig
Custom CI/CD Orchestrator for Railway
Stop fighting with rigid deployment pipelines. I will build you a custom, Node.js-powered CI/CD Orchestrator designed specifically for Railway Cloud.
Unlike standard GitHub-linked deploys, this solution gives you total control. I'll set up a central "brain" that receives webhooks, processes your logic, and triggers deployments via Railways GraphQL APIno direct GitHub linking required.
Whats Included:
- Custom Orchestrator: A secure Node.js server to manage your workflow.
- Docker-to-Railway Pipeline: Push-based deployment for microservices.
- Security First: Webhook verification and secret management.
- Zero-Downtime: Automated rolling updates via Railway's infrastructure.
Scale your microservices with a deployment flow that finally fits your architecture. Lets automate your cloud today!
Tools:
Docker
•
GitHub
•
Other
Frameworks:
Npm
•
Other
Cloud Provider:
Other
Programming language:
JavaScript
Expertise:
Debugging
•
Development
•
Other
My Portfolio
FAQ
Do I need to link my GitHub account directly to Railway?
No! That is the primary benefit of this service. We use a custom orchestrator that handles the code or Docker images independently. This gives you more privacy and allows for custom logic (like testing or security scans) to happen before the deployment is triggered via the Railway API.
What do I need to provide to get started?
I will need your Railway API Token (found in your account settings) and the Service ID of the application you want to automate. If we are using a private Docker registry (like GHCR), I will also need the necessary pull credentials to configure the service.
Can the orchestrator handle multiple microservices?
Absolutely. The Premium package is designed for multi-service architectures. The orchestrator can act as a central hub, receiving different webhooks and routing the correct build and deployment commands to various Railway services based on your specific rules.
Is the orchestrator secure?
Yes. I implement webhook signature verification (HMAC) to ensure that only legitimate requests from your GitHub repository can trigger a deployment. Your API tokens are handled as environment variables and are never hardcoded into the script.
Will there be downtime during the deployment?
No. Railway uses a rolling deployment strategy by default. The custom orchestrator triggers the build, and Railway only switches traffic to the new "Healthy" container once it passes its internal health checks, ensuring zero downtime for your users.
