Not able to deploy Logto
kulterryan
PROOP

a year ago

I'm not able to deploy logto on railway, I've deployed and seeded the DB as described in the docs before deployment using Logto global CLI but it keeps throwing error for DB alternation.

Docs: https://docs.logto.io/logto-oss/get-started-with-oss
DB Alternation Docs: https://docs.logto.io/logto-oss/using-cli/database-alteration

16 Replies

kulterryan
PROOP

a year ago

PFA Error Log

Attachments


unicodeveloper
PRO

a year ago

This seems like you haven't run the commands described in the database alteration docs.


Status changed to Awaiting User Response Railway about 1 year ago


kulterryan
PROOP

a year ago

I've added that in dockerfile also, and tried to deploy from updated docker file but it's not working.


Status changed to Awaiting Railway Response Railway about 1 year ago


unicodeveloper
PRO

a year ago

Can I see what the Dockerfile looks like?


Status changed to Awaiting User Response Railway about 1 year ago


kulterryan
PROOP

a year ago

PFA.

Attachments


Status changed to Awaiting Railway Response Railway about 1 year ago


unicodeveloper
PRO

a year ago

  1. why are you not using this? npx @logto/cli db alteration deploy

  2. Run Docker locally with this and check the results


Status changed to Awaiting User Response Railway about 1 year ago


kulterryan
PROOP

a year ago

Sure.


Status changed to Awaiting Railway Response Railway about 1 year ago


kulterryan
PROOP

a year ago

I tried, locally it's working but not on railway.


kulterryan
PROOP

a year ago

Can you please help me with a template or something? I exposes two ports, 3001 & 3002, I feel, railway is not able to expose the ports properly.


a year ago

Can you please link to your latest deployment of logto?



a year ago

Looks like npm run alteration deploy is never exiting and thus preventing the server from starting.


kulterryan
PROOP

a year ago

In deploy logs, you can see it has exited with info Found 0 alteration to deploy


a year ago

You are correct, my apologies for the incorrect assignment.

I see that the start command needed to be wrapped in a shell because && is shell specific.

The deployment now runs both commands, yet logoto still says there are undeployed database alterations despite the previous printout saying there are no alterations to deploy.

Unfortunately, this is where my knowledge runs out, I think you could get better help with logto from the logto community or developers than I could provide you with.


kulterryan
PROOP

a year ago

Hi Brody,
Issue with undeployed database alterations is resolved, but it seems railway is still not able to recognize the ports allocated to the respective domains.


a year ago

Hmmm, I'm not sure why you say that, from your latest deployment -

error Found undeployed database alterations, you must deploy them first by npm run alteration deploy command.

And the deployment, despite saying active has exited.


Loading...