Hey Rees,

I just ran this template and everything is working nicely.

Well done!

When updating the image, there might also be db migrations.

Logto has a page for db updates. https://docs.logto.io/logto-oss/using-cli/database-alteration

They have a command to auto run this for us

npm run alteration deploy latest

To include this in the app startup process, I found that modifying the startup command to be

sh -c "npm run cli db seed -- --swe; npm run alteration deploy latest; npm start"

This should help us auto run db migrations

Hey starvingdogs, thanks for the suggestion! I've updated the template with that new command

 
=========================
Container failed to start
=========================
 
/orchestrator.RouterLegacyService/CreateDeployment UNKNOWN: initializing source docker://bitnami/redis:7.2.5: reading manifest 7.2.5 in docker.io/bitnami/redis: manifest unknown
 

please change redis service bitnami/redis:7.2.5 dont see version.

Thanks for pointing this out @productdevbook! I've updated the template to use a different Redis image.

Hi! Do you have an estimate of how much this setup cost? And why are the auth and admin separated into two processes?

I get this error in logto-admin-console upon trying to deploy this template.
```
Error: getaddrinfo ENOTFOUND postgres.railway.internal

at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:122:26) {

errno: -3008,

code: 'ENOTFOUND',

syscall: 'getaddrinfo',

hostname: 'postgres.railway.internal'

}
```
I read somewhere that the internal network is unavailable during build stage.
Are we running migrations during the build stage?

I just ran the template myself on a new project and can't replicate that issue. Have you changed any settings by any chance?

Sorry for the the late reply! I don't have any usage data myself to share, but the docs recommend 2 vCPUs, 8GiB memory, and 256GiB disk space. It's running as two processes because the admin console and auth screen run on different ports :)