Closed jasoncavanaugh closed 1 year ago
This PR is being deployed to Railway 🚅
admin-portal: ◻️ REMOVED
I triggered it to redeploy in Railway and same thing, still no URL
I manually generated a url in Railway. But I got the "Please set NODE_ENV to 'production'" message. Did you change the deployment to use "development" for PRs?
I manually generated a url in Railway. But I got the "Please set NODE_ENV to 'production'" message. Did you change the deployment to use "development" for PRs?
I don't remember setting that but it was set to use "dev" and other development env vars. I changed to the prod ones and it's working now. I'll see where that came from, if it's a global PR setting. I was trying to set that for the other deployment that's intended to stay connected to DEV stuff, but might have done to the wrong one.
I manually generated a url in Railway. But I got the "Please set NODE_ENV to 'production'" message. Did you change the deployment to use "development" for PRs?
I don't remember setting that but it was set to use "dev" and other development env vars. I changed to the prod ones and it's working now. I'll see where that came from, if it's a global PR setting. I was trying to set that for the other deployment that's intended to stay connected to DEV stuff, but might have done to the wrong one.
Ok, here's where that happened. The PRs were set to inherit from the new development-base project that I intended to have point to dev stuff. But, there are other issues with that still with the NODE_ENV thing when deloyed on Railway, so i'll change that back to production for now.
Also changed NODE_ENV check to check against "development" because that is how it is everywhere else in the code.