Migrate from Render to Railway Guide (#647)

* Ad migrate from Render guide

* add migration

* Update

next-env.d.ts

@@ -2,4 +2,4 @@
 /// <reference types="next/image-types/global" />
 
 // NOTE: This file should not be edited
-// see https://nextjs.org/docs/basic-features/typescript for more information.
+// see https://nextjs.org/docs/pages/building-your-application/configuring/typescript for more information.

src/data/sidebar.ts

@@ -290,6 +290,12 @@ export const sidebarContent: ISidebarContent = [
       makePage("Compare to Render", "maturity"),
     ],
   },
+  {
+    title: "Migration",
+    content: [
+      makePage("Migrate from Render", "migration"),
+    ],
+  },
   {
     title: "Community",
     content: [

src/docs/maturity/compare-to-render.md

@@ -4,6 +4,8 @@ title: Railway vs. Render
 
 Railway is a modern, developer-focused cloud platform that simplifies app deployment and scaling. We are optimised for developer happiness and efficiency!
 
+**Note:** [Migrate your app from Render to Railway in less than 4 steps.](/migration/migrate-from-render)
+
 We are similar in the following ways:
 
 - GitHub repo deployments

src/docs/migration/migrate-from-render.md

@@ -0,0 +1,79 @@
+---
+title: Migrate from Render to Railway
+---
+
+This guide walks you through the steps needed to seamlessly migrate your app and data from Render to Railway.
+
+With features like instant deployments, CI/CD integrations, private networking, observability, and effortless scaling, Railway helps developers focus on building rather than managing infrastructure.
+
+Railway boasts of a superior and intuitive user experience that makes deploying complex workloads easy to configure and manage.
+
+Railway offers:
+
+- **Broad Language and Framework Support**: Deploy apps in [any language or framework](https://docs.railway.com/guides/languages-frameworks).
+- **Flexible Deployment Options**: Use GitHub, Dockerfiles, Docker images from supported registries (Docker Hub, GitHub, RedHat, GitLab, Microsoft), or local deployments via the Railway CLI.
+- **Integrated Tools**: Simplify environment variable management, CI/CD, observability, and service scaling.
+- **Networking Features:** Public and private networking.
+- **Best in Class Support:** Very active community on [Discord](https://discord.gg/railway) and [Help Station](https://help.railway.com/).
+
+..and so much more. Want to see for yourself? [Try Railway for a spin today!](https://railway.com/new)
+
+## Migration Steps
+
+In this guide, we will migrate a Go (Beego) app with a Postgres database from Render to Railway. 
+
+Here’s the link to the app. A simple chat app that have the options of Long polling and Web socket — https://github.com/unicodeveloper/beego-WebIM 
+
+### 1. Set Up a Railway Project
+
+Navigate to [Railway's Project Creation Page](https://railway.com/new). 
+
+Select the **Deploy from GitHub Repo** option and connect your repository. If your Railway account isn’t linked to GitHub yet, you’ll be prompted to do so.
+
+![Set up a Railway Project](https://res.cloudinary.com/railway/image/upload/v1736366540/newproject_ljvsqp.png)
+
+### 2. Deploy the App
+
+Railway automatically detects a `render.yaml` file in your repository and provisions the corresponding services, including databases, web (both public and private), crons, and workers.
+
+If environment variables are defined in your `render.yaml`, Railway will import them automatically to the appropriate services. If they are not defined, you can manually migrate them by following these steps:
+
+**On Render**:
+
+1. Go to the **Environment Variables** page of your service.
+2. Copy all the variables and their values.
+
+**On Railway**:
+
+1. Open the **Variables** section for the relevant service.
+2. Switch to the **Raw Editor** and paste the copied environment variables.
+3. Deploy the changes to apply the configuration.
+
+![Deploy on Railway](https://res.cloudinary.com/railway/image/upload/v1736366539/deployapp_rlhvzx.png)
+
+Railway will deploy both the Go app as a service and the database, as shown in the image above. You can monitor the service building and deploying in the [Project Canvas](https://docs.railway.com/guides/projects#project-canvas).
+
+### 3. Database Migration
+
+Railway supports a variety of databases, including **PostgreSQL**, **MongoDB**, **MySQL**, and **Redis**, allowing you to deploy the one that best fits your application needs.
+
+When a `render.yaml` file includes a `databases` section, Railway will automatically provision a **PostgreSQL database** for your app. If you're migrating data to Railway, you can follow these steps:
+
+1. Export your database from Render using tools like `pg_dump`.
+2. Import the data into Railway using `psql`.
+
+For detailed instructions, check out [this comprehensive tutorial on migrating PostgreSQL data between services.](https://blog.railway.com/p/postgre-backup)
+
+Once the migration is complete, update the `DATABASE_URL` environment variable in your Railway app to point to the new PostgreSQL database.
+
+### 4. Multi-region deployments
+
+If your app needs to use multi-region deployments, you can leverage Railway’s [multi-region replicas](https://docs.railway.com/reference/scaling#multi-region-replicas). 
+
+Enable this in the **Settings** section of your Railway service to keep your app close to users worldwide.
+
+**Note:** Multi-region replicas is currently available to Pro users.
+
+![Multi-region deployments](https://res.cloudinary.com/railway/image/upload/v1736366540/multiregiondeployments_pojcyf.png)
+
+And that’s it. That’s all you need to migrate your app from Render to Railway.