New Builder Doesn't Automatically Detect /web Directory
Project Link: https://railway.app/project/7ea7fbfa-fd31-463b-a6a9-aeede9da76dc
When deployed with the new builder, nginx returns a 403 with the following error in the console:
When not using the new builder, it detects the /web directly properly and deploys without issue.
Railway
Railway
Railway is an infrastructure platform where you can provision infrastructure, develop with that infrastructure locally, and then deploy to the cloud.
29 Replies
Project ID:
7ea7fbfa-fd31-463b-a6a9-aeede9da76dcThanks percy <3
can you share your repo?
GitHub
GitHub - SDCore/sdcore.dev
Contribute to SDCore/sdcore.dev development by creating an account on GitHub.
Nothing special atm, but it's happened with a few projects I've tried to deploy with nginx
I'm surprised this even worked on the legacy builder
No config but that wasn't a problem pre-new builder
:kekko:
It also detects port 9000 when trying to generate a domain even tho it starts with port 8080
Dunno if thats related at all :3s_shrug:
port 9000 is likely php-fpm
it do say that but i didnt know what it meant :yon_Nod_yes:
do you have any kind of service level config?
Other than generating a domain I don't change anything from the defaults
V2 runtime and w/ the new builder
build logs for a build done with legacy and build logs for a build done with the new builder please - https://bookmarklets.up.railway.app/log-downloader/
old builder
new builder
old bookmarklet detected