Sam
Custom domain stuck on "Issuing TLS certificate"
Hi, I am moving my production site over to Railway from Vercel and it has been down for almost 24 hours now with this issue. I have added custom domains to Vercel many times in the past and it hasn't ever taken more than like 10 min which is why I am concerned theres a bug. I have tried deleting and re-adding the domain.
38 replies
Issues with Root Directory and NextJS deployment in Turbo repo
I have a turbo monorepo with a Next app I am trying to deploy. I need the paths for deployment to be as follows:
Deploy:
./apps/website
Build: ./
Install: ./
Variables: ./apps/website
Solution 1
- Set the Root Directory as ./
- Set the install phase cmd to npm install (executes in ./ as desired)
- Set the buildCommand to npm run build (executes in ./ as desired)
- Set the startCommand to npm run --prefix ./apps/website start (executes in ./apps/website as desired)
Problem: It attempts to load the ENV Variables at ./apps/website when Railway thinks they are at ./ since thats what was specified as the Root Directory
Solution 2 (Ideal solution)
- Set the Root Directory as ./apps/website
- Set the install phase cmd to npm install --prefix ../..
- Set the buildCommand to npm run --prefix ../.. build
- Set the startCommand to npm run start (executes in ./apps/website as desired)
Problem: Railway seems to do some COPY . /app/. process which makes any path outside the specified Root Directory inaccessible (ie ../../package.json or the path ./package.json in my monorepo does not exist) and therefore impossible to execute the install and build commands in the right path
Solution 2 is my idea situation since it scopes the deployment to the code that I want, this is how it works on Vercel.
I guess the two potential changes I would need are either:
- (ideal) Some way to change the directory at which Railway runs the COPY . /app/. command to COPY ../.. /app/.
- Some way to change the path at which the ENV Variables are loaded14 replies