August 2022 Summaries

You can use GitLab CI/CD to automate your deployments on Railway by creating a project token and adding it to your repository secrets, then defining a workflow that triggers on pushes to the default branch, using the Railway CLI as a base image for a job that deploys to a service defined by the service ID. The entire building part is handled by Railway's build infrastructure, but you can still use GitLab CI to deploy build artifacts to Railway. It's recommended to keep the RAILWAY_TOKEN secret and pass the service ID freely as an environment variable or as part of the deploy command.

Migrating From Heroku To Railway Moving your app can be stressful, but Railway makes it easy. Railway is a simple and powerful deployment platform that supports over 20+ languages and runtimes. It offers GitHub Repo Deployments, a CLI that lets you do everything the Web App does, built-in databases, PR deploys, secrets management, speedy quick builds, resource-based pricing, interfaces, community support, and more. Railway allows users to import environment variables from Heroku, set up database services, and use Procfiles for process scheduling and management. The platform provides a Project Canvas where services are deployed, and DBs have Table View GUIs, Manual Queries, and much more. Railway also offers built-in horizontal scaling, the ability to pull down variables locally, and a CLI that triggers new deploys with `railway up`.

Railway now supports Cron Jobs natively, allowing users to deploy their cron jobs easily using language-level libraries. Railway treats all deployed services, including cron jobs, as equal and deploys them automatically with no additional configuration needed. Users can create a new project on Railway and deploy their cron service in just one click. The deployment process uses the node-cron library for JavaScript applications.