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

Hi @Brody , I'm going to create a new Template with all the latest hotness. Busy checking out all the new updates to Templates since we last spoke and had a question:

Is it possible to create a configurable template that, when the user deploys it, will conditionally include either postgres, mongodb or mysql depending on some config the user specifies on the template deploy config page?

I don't think this is possible, so I'll probably create powersync-mysql, powersync-mongodb, powersync-postgres, etc templates. Just checking that I'm on the right track 🙂

Unfortunately from what i know it isnt possible to optionally change databases.

This is definitely some tooling for templates though which i’d like to see

What Noah said, you would have to create seprate templates.

Thx!

Hey @k0b13 - We would love for you to become a template partner, you already have the template, and your templates are already published by your own PowerSync workspace.

You can apply here - https://railway.com/partners

And I am also happy to answer any questions you may have!

Awesome, thanks! I'll apply. I got the new stack working yesterday in a new project, it's now just bundling, shipping and some light docs on our end before I can publish the new templates.

Amazing! Please do apply, and we can get your partnership set up and your templates verified!

And please let me know when the templates are ready for review! 🙂

our service accepts env vars as base64 encoded since the config is quite chonky, so encoding a config file into base64 will be one manual step to use the templates, but otherwise it's looking very promising compared to the current template

also briefly checked out volumes but no luck alas

I'm a sucker for automation

No luck with volumes? anything I could help with?

Nope, more just that what I was thinking is something Railway doesn't support (basically creating a volume and then editing a config file on the volume from the Railway dashboard, but I know this is not a supported use case)

Ah, yeah, not something we support, unfortunately.

Last thing I'd like to get going is a healthcheck

The service boots and our healthcheck endpoint returns 200

The service boots and our healthcheck on /probes/startup returns 200

I then configure it on the service (manual testing for now, will drop it into the template later)

but that just fails to succeed

probably trying to connect on the wrong port or something, digging around in docs…

That red info text may take you to the applicable docs.

ah yeah was missing a PORT, solved - thanks

No problem!

Hey @Brody 👋

I am part of the PowerSync team and have been building the new template. Everything is working well but there is a bit of manual intervention required and I was wondering if it could be automated.

There are 5 main services:

• Postgres Data Source - main database

• Postgres Bucket Storage - storage database

• Node.js Backend - backend api that is configured with public networking

• PowerSync Service - configured with public networking

• Execute Scripts (bun function) - this creates the necessary tables, seeds them and creates the powersync publication in the Postgres Data Source

When deploying the template, the PowerSync Service fails because the user must base64-encode a .yaml template file and set it as the value of the POWERSYNCCONFIGB64 environment variable.

They need insert the following values into the template and base64-encode it:

• ${{"Postgres Source Data".DATABASE_URL}}

• ${{"Postgres Bucket Storage".DATABASE_URL}}

• The Node.js backend public url

• The PowerSync Service public url

And then set the base-64 encoded string to the {{"PowerSync Service".POWERSYNCCONFIGB64}} environment variable.

My question is, is there a way to automate this? Perhaps by using another function?

We don't have a function to base64 encode something, the best way I can think of would be to move away from base64 encoding and allow for configurations to be done via individual environment variables.

I think I would be able to do it in a bun function but I'm not sure how to get all of those values I need inside the template string and also I am not sure how I can set the {{"PowerSync Service".POWERSYNCCONFIGB64}} variable from a function or if it is possible.

I would recommend allowing power sync to be configured with environment variables instead of base64 encoded yaml

That's going to be easier for the Railway template, and anyone self hosting powersync outside of Railway as well.

Hey @Brody 👋

Quick question, how exactly are the arrows created? Is it just when a service references another services environment variables?

I can't find anything concrete in the documentation on this. I see at the bottom of this changelog it mentions that it's also when you have Service Groups enabled.

Yes, it is based on reference variables.