Zvezke Comments - Answer Overflow

Topics

Zvezke

Explore posts from servers

KPCKevin Powell - Community RRailway

•Created by BruceX on 6/13/2024 in #✋｜help

Waiting for CI 3 hours ago via GitHub(can not deploy)

... never mind - I fixed it (which was a temporary deployments in context of pull requests) by 'Runtime - How your app is deployed' to 'V2'.

7 replies

•Created by BruceX on 6/13/2024 in #✋｜help

Waiting for CI 3 hours ago via GitHub(can not deploy)

Hmm ... I seem to be stuck with the same problem. How do I re-push in Railway or VS Code? In Railway, I don't see any option to redeploy.

7 replies

•Created by Zvezke on 4/26/2024 in #✋｜help

Accidently closed post - how do I reopen?

Solved. Sorry for the inconvenience - I've reopen the post. I'll mark this as solved, but leave it open. An extra can of Carlsberg is coming your way.

7 replies

•Created by Zvezke on 4/26/2024 in #✋｜help

Accidently closed post - how do I reopen?

N/A

7 replies

•Created by Zvezke on 4/26/2024 in #✋｜help

Deployment of NextJS project has suddenly started failing - ERR_PNPM_NO_LOCKFILE

Btw, I'm guessing pnpm v9 will work eventually ... ?

11 replies

•Created by Zvezke on 4/26/2024 in #✋｜help

Deployment of NextJS project has suddenly started failing - ERR_PNPM_NO_LOCKFILE

Solved. Thanks a lot, Brody. You once helped me work out a dockerfile for one of my projects. As a token of my appreciation, I promised you Carlsberg and Scandinavian women in return - now even more Carlsberg and Scandinavian women are coming your way. 🙂 I've marked this as solved, but I don't know how to mark your reply as the answer.

11 replies

•Created by Zvezke on 4/26/2024 in #✋｜help

Deployment of NextJS project has suddenly started failing - ERR_PNPM_NO_LOCKFILE

Oh, so I just have to downgrade.

11 replies

•Created by Zvezke on 4/26/2024 in #✋｜help

Deployment of NextJS project has suddenly started failing - ERR_PNPM_NO_LOCKFILE

c7772db3-fb07-4266-908a-2140c144bf67

11 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

Initially, you suggested 'RUN apk ... pnpm ... ', but that didn't work. The file works now. I am just wondering what is causing a normal deployment to fail. It's just my curiosity - don't worry about it. Thanks, much appreciated - I'll see you in the threads. And I'll get back if things fail again. 🙂

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

The dockerfile works - all is fine again.

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

Well, adding packages (libvips in different variations) to nixPkgs didn't help - finally, you suggested a docker file.

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

Initially, I got "gyp ERR! find Python" - adding "python38" to railway.json worked. Then, I got the same (as mentioned in this thread) the missing "gcc" error. "gcc" added, but deployments started failing due to missing "libvips". Adding libvips (in all different variations) didn't work - pkg not recognized. Then, I asked for help, and here we are ...

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

Btw, do you know if this is a bug in Railway?

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

... so actually - running 'npm install -g pnpm' separately did it (compared to you first suggestion).

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

It works - thanks. I really appreciate it. I'll buy you two beers next time you're in Copenhagen - two Carlsbergs, of course. And I'll introduce you to Scandinavian women as well.

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

Thanks. I'll be back i five.

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

FROM node:18.19.0-alpine

ARG NEXT_PUBLIC_RAILWAY_URL NEXT_PUBLIC_POCKETBASE_URL NEXT_PUBLIC_RAILWAY_URL NEXT_PUBLIC_SUPABASE_ANON_KEY NEXT_PUBLIC_SUPABASE_URL

RUN apk add --no-cache openssl build-base python3 vips-dev

WORKDIR /app

COPY package.json ./

RUN npm i

COPY . ./

RUN npm run build

CMD npm run start

FROM node:18.19.0-alpine

ARG NEXT_PUBLIC_RAILWAY_URL NEXT_PUBLIC_POCKETBASE_URL NEXT_PUBLIC_RAILWAY_URL NEXT_PUBLIC_SUPABASE_ANON_KEY NEXT_PUBLIC_SUPABASE_URL

RUN apk add --no-cache openssl build-base python3 vips-dev

WORKDIR /app

COPY package.json ./

RUN npm i

COPY . ./

RUN npm run build

CMD npm run start

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

If possible, yeah. I assume using the same pkg-manager is less prone to bugs.

108 replies

•Created by Beggars on 5/25/2023 in #✋｜help

Node.js 18 and node-gyp compatibility

Hey! It's alive! 🙂 Thanks a billion - I'll buy you a beer next time you're in Copenhagen, Denmark - Carlsberg, of course.

108 replies