I've got an app that works correctly localhost, but when I deploy to Railway, the only thing I get is the app error page shown.
I've checked the logs and there aren't any errors. How do you debug this?
#Payload CMS App Doesn't Appear to work correctly
reef bough
glass relicBOT
late lark
please see this docs page - https://docs.railway.app/guides/fixing-common-errors
reef bough
please see this docs page - <https://docs.railway.app/guides/fixing-common-error...
Thanks. The Railway service didn't add a port, so I manually added one and it's working as expected.
late lark
It's not supposed to, as mentioned, your app should listen on the PORT environment variable
reef bough
Good to know, because the docs say otherwise. I found this text on the page. I checked for the Railway-provided variables and didn't find port listed.
Thus, your web server must listen on host 0.0.0.0 and the port that Railway provides in the PORT environment variable.
late lark
it's not provided in the service variables, it's automatically generated for your app when you deploy
as you can see, the approach you took is not recommended
reef bough
as you can see, the approach you took is not recommended
I see that.
reef bough
it's not provided in the service variables, it's automatically generated for you...
If it's not an ENV variable, then what is it, and where do I find it?
late lark
it is an environment variable, I'm not sure where the confusion is coming from?
as that docs page states, your app simply needs to listen on the environment variable PORT
reef bough
I see what you're saying now. I was reading it inversely. Like I need to find the port in Railway and set that up in my app.
sudden spearBOT
reef bough
Fixed it in my app, and redeploying now. Will close if all is well.
late lark
please do not close threads
reef bough
Ok. Sure. Just curious as to why you wouldn't want them closed.
late lark
closing threads on discord hides them
reef bough
That's interesting. I've never seen that happen before. Maybe it's a config thing? Not sure.
On the Nest.js server, we close threads when problems are solved. It just moves it down to a different section. On there, the threads are structured like this:
Open Threads
Older Posts (closed threads)
So, when you close it, they just move down. Both also show up in search as well.
late lark
not sure, I didn't set it up, all I know is that when a user closes their thread it looks like it has disappeared, for us we mark the thread as solved with a tag