An repo for easily deploying Rocket.Chat into Railway using Dockerfiles.

The reason why we made this is forking the official repo and deploying into Railway can be an distater due to the missing meteror executable.

1. Click the Deploy on Railway below to get started.

2. In the Where should the new repo live?, leave it as is. If you created that repo, see next section instead. You can also create a new repo to your GitHub org instead.

3. Confirgure environment variables as you like. Here are some docs:

   • Replace the value of MONGO_OPLOG_URL with the MongoDB URL of your instance. It can be your other Railway project if you want.
   • For the ROOT_URL, if you planning to use custom domain, then please replace the placeholder with real values. Otherwise, make sure you remove the ROOT_URL variable in the Variables page.

4. Hit deploy and cross your fingers! Railway should redirect you into your shiny app dashboard for your Rocket.Chat instance.

5. Navigate into the Deployments screen and check if the latest deployment is now Deployed. If stuck at Deploying after few minutes, check the logs then file a new issue here. If it's configuration problem on your variables, fix it first.

6. Visit your Rocket.Chat instance and register. The first user to be registered should automatically granted adminstrative powers.

7. Profit!

WIP

• Rocket.Chat requires either oplog or replicaset to run, as per https://docs.rocket.chat/installation/manual-installation/mongo-replicas/. The only current workaround is setup another MongoDB instance in another Railway project or elsewhere with replicaset enabled. And since this is untested on Railway-hosted MongoDB instances, prepare for the worst case scenario.