https://railway.app/template/RfZi6y?referralCode=2vw_V9

currently out Christmas shopping for the day so I'll look at it when I'm back home!

No rush! On my way out too

im seeing
DATABASE_HOST=postgres.railway.internal
and
DATABASE_PORT=5432
on the powersync-nodejs-backend service, instead, on the postgres service set these variables
PGHOST_PRIVATE=${{RAILWAY_PRIVATE_DOMAIN}}
and
PGPORT_PRIVATE=${{RAILWAY_TCP_APPLICATION_PORT}}
and then reference those new variables on the powersync-nodejs-backend service

when I edit the template and make those changes, the button at the bottom says Fork Template, that doesn't seem right

uhhh you made this template on your team didn't you

yeah

that's bugged right now 😬

haha I feel you

so fork and delete old one?

you can't delete it either I don't think

but try

Yep can confirm

welp, fix coming in 2024

the majority of the team is on vacation

nice time of year to say that

fix could be round the corner!

haha yeah not ideal, but there's not much I can do for bugs that don't affect users workloads

yep same… all good, worst case if a developer uses it, I can help them update these vars in their deployed project

I mean it would still work just fine

yeah

I was able to update the description a bit to include some more info on what the template does, so there's that. Anyway, appreciate all the help thus far and happy holidays 🙂

no problem, always happy to help when templates are involved

and happy holidays to you too

Thanks!
p.s. The Deploy button totally fits into the color scheme of our docs https://docs.powersync.com/integration-guides/railway-+-powersync

I noticed, it looks great!

@Brody We’re gearing up to release our Open Edition by the end of May which will let customers run full-stack Postgres+PowerSync+Backend on Railway and I want to get your input on our updated Template since it seems we've had nonzero downloads of the previous one. Can I still msg you here when it's ready for a review?

(previous Template was Postgres + Backend connected to hosted PowerSync, the update will make it fully self-hosted on Railway with no external deps)

absolutely!

are mongodb replicasets supported using the stock mongodb?

they do not, it's something you'd have to setup yourself, and I've heard mongo does not make it easy

I have a docker-compose config that sets it up, might give it a whirl

    entrypoint:
      - bash
      - -c
      - 'sleep 10 && mongosh --host mongo:27017 --eval ''rs.initiate({_id: "rs0", version: 1, members: [{ _id: 0, host : "mongo:27017" }]})'''

oh, you mean mongo doesn't make it easy on Railway

never hardcode the host and port like you're doing there

yup!

mongo doesn't make it easy even in a docker compose file lol