a year ago
Hello.
I am trying to move my Astro site from Vercel, where it is currently working without problems (except for some bug in the Vercel integration that makes impossible to build static pages) to railway.
I created a docker image and managed to make it build properly. The site is deployed and available, but for some weird reason one of the routes that points to a static path is redirecting me to localhost. When I click the link first I see a white screen saying that I will be redirected to localhost, and them I am redirected to localhost.
Any idea why? Is this something Railway load balancer does?
0 Replies
Hey! Mind sharing a link? It doesn't look like something that neither Astro or Railway usually do
Check the first link https://boda-ali-dani-production.up.railway.app/
By the way, I fixed the redirect by providing the public url of the site to Astro, so at least it now redirects to the right place
When testing this inside docker in my local machine accessing that url makes the server crash, which is why I assume the redirect happens
a year ago
vercel will automatically intercept redirects to localhost and change them to redirect to the public address, railway will not do anything of the sort, when running on railway your code must send the correct redirect response
The app does not crash on Vercel, and no redirect happens, the right route is displayed
On railway there are no logs when I hit that route wich make me suspect the app crashes, and as I mentioned in docker in my local machine it crash
a year ago
let's see your dockerfile
FROM node:18-slim AS base
ENV PNPM_HOME="/pnpm"
ENV PATH="$PNPM_HOME:$PATH"
RUN corepack enable
COPY . /app
COPY astro.node.config.ts /app/astro.config.ts
WORKDIR /app
FROM base AS prod-deps
RUN --mount=type=cache,id=s/0cdba51f-ca18-4991-b228-f30672040b04-pnpm,target=/pnpm/store pnpm install --prod --frozen-lockfile
FROM base AS build
ARG POSTGRES_URL
ARG SITE_URL
RUN --mount=type=cache,id=s/0cdba51f-ca18-4991-b228-f30672040b04-pnpm,target=/pnpm/store pnpm install --frozen-lockfile
RUN pnpm run build
FROM base
COPY --from=prod-deps /app/node_modules /app/node_modules
COPY --from=build /app/dist /app/dist
ENV HOST=0.0.0.0
ENV PORT=4321
EXPOSE 4321
CMD node ./dist/server/entry.mjs
a year ago
i see you are doing a whole lot of stuff that isnt absolutely necessary, please get a minimal dockerfile working first
a year ago
no
a year ago
no
I was using a dockerfiie for portability in case I want to go another place. But will try without a dockerfiie
How do I force it to be a node server? It automatically detects the dockerfiie and uses it
a year ago
remove or rename the dockerfile
I changed to custom build and run commands. Does that suffice ? The problem persists
a year ago
what are your custom build and start commands?
Just removed the dockerfile. The build now fails.
My custom build is:
pnpm build
My custom run is
node ./dist/server/entry.mjs
Now that I removed the dockerfile it fails to build:
15.05 [commonjs--resolver] Failed to resolve entry for package "flowbite-svelte". The package may have incorrect main/module/exports specified in its package.json: No known conditions for "." specifier in "flowbite-svelte" package
a year ago
full build logs please
a year ago
fix your typo please, i dont understand the question
a year ago
its just drag and drop?
a year ago
i use chrome
a year ago
remove the install command from your build command please
a year ago
yes please
a year ago
what node version are you using locally
a year ago
you do use pnpm locally right
a year ago
there are no errors duing the install phase
a year ago
can you run pnpm build
locally without issues?
a year ago
are you making sure node_modules and the built files arent making it into your repo
Yes, both configs build locally fine
a year ago
you ran a different build command than what you are telling railway to run
a year ago
this error wouldnt be isolated to railway, have you tried searching for solutions to the error?
a year ago
unless you want to use railway's api directly, yes
I isolated the problem to be an issue with Astro hybrid mode. For some reason, when running on hybrid mode is not following the normal flow for pages that are not found, and crashes. Using server mode doesn't suffer from that problem