A one-click deploy Railway template for Milvus

[monotykamary]

This is a template I've made for Milvus for anyone interested in a one-click deploy to try it out:

https://railway.com/template/c7nLmV?referralCode=ZqgrJ0

It should work great, but feel free to comment if you have any issues using it. It's a template that's perfect basic self-hosting as well as a place to test the waters before you decide to scale with Zilliz cloud.

[yhmo]

I didn't make it work, I got an error from Nixpacks

[monotykamary]

Oh I'll have a look; this should use docker all the way down 🤔

[monotykamary]

Ah, it seems you're running railway up and overwriting the standalone service. railway up will deploy your code in your current directory linked to a service you select. If there isn't a Dockerfile, it will use Nixpacks to figure out what your app is and deploy an appropriate config for it.

[balcklive]

I can't connect it what is the default deploying port?

[monotykamary]

It should be 9091. There is the rare case where once in a blue moon Railway will just straight up not assign that assigned PORT to the HTTP endpoint. Is https://standalone-production.up.railway.app/webui/ accessible for you?

[balcklive]

In my case, https://standalone-production.up.railway.app/webui/ is accessible. But I cannot connect the database with python sdk with code below:

from pymilvus import connections

connections.connect(
    alias="default",
    host='ballast.proxy.rlwy.net',
    port='29197'
)

# ballast.proxy.rlwy.net:29197

print("connect successfully:", connections.get_connection_addr("default"))

[monotykamary]

Ah that one is a bit on me, I did assume interactions with Milvus here would be internal. Somewhat unfortunately that even though Railway supports HTTP/2, the TCP proxy it uses demuxes it to HTTP/1.1. The current workaround is to use a GRPC reverse proxy; I've made a quick one to use: https://github.com/monotykamary/grpc-reverse-proxy

Create a new service using a docker image and point it to ghcr.io/monotykamary/grpc-reverse-proxy:latest.

Set these variables in your grpc-reverse-proxy service:

PORT="8080"
SERVICE_URL="${{standalone.RAILWAY_PRIVATE_DOMAIN}}:19530"

Once deployed, set public networking for it:

Running the script to point to the new URL should work.

from pymilvus import connections

connections.connect(
    alias="default", uri="https://grpc-reverse-proxy-production.up.railway.app:443"
)

print("connect successfully:", connections.get_connection_addr("default"))

connect successfully: {'address': 'grpc-reverse-proxy-production.up.railway.app:443', 'secure': True, 'user': ''}

---

I have updated the template to use this reverse proxy as well. I'll likely add some default authentication given the more public setup.

[balcklive]

OK, thank you for your update, I have tried the latest template on railway, and it worked!