How do you update the migrations after this is deployed?

This is more of a starting point, if you want to have your changes take place there is a script that runs the migrations when you build the project. Otherwise see the payload docs you have more of a specific need https://payloadcms.com/docs/database/migrations

So should we fork your repo before deploying? what's the happy path to get this setup properly?

• Enable Template Service Eject -> https://railway.app/account/feature-flags

• Deploy template.

• Eject from template in the service settings.

Thanks brody and madebyjonny

• Enable Template Service Eject -> https://railway.app/account/feature-flags

• Deploy template.

• Eject from template in the service settings.

Just tried this, but im not what this does. I see an eject button for the upstream repo, but I think i want my source repo to be changed here. In general, should i be forking off these templates for customization then updating Railway with the new source repo?

should i be forking off these templates for customization then updating Railway with the new source repo?

This is exactly what the Eject button does for you, It clones the repo and auto updates the source to the newly made clone.

should i be forking off these templates for customization then updating Railway with the new source repo?

This is exactly what the Eject button does for you, It clones the repo and auto updates the source to the newly made clone.

Ah this is so cool! works now!

Hey! Could u bump the deps version? There’s a major update coming soon to payload.

Yeah I'll do that tonight

Hey! Could u bump the deps version? There’s a major update coming soon to payload.

Should be all updated to the latest. I am keeping an eye on Payload v3.0 to.