ProjectID:

2b6e2b92-e5d7-4be3-abf3-8524f4292c61

Just had a hiccup of the javascript loading momentarily, but the static images did not load. I made an update to remove static image (use hosted elsewhere) and now the js is broken again.

When the JS was loading properly, was working on vivaldi but not chrome. On both i used incognito tabs with storage wiped.

Very bizzare, tricky to debug

heres a video demonstrating the issue of components that need javascript (days until counter in top left uses new Date, and the dropdown a simple state boolean)

1354536937955791110

also shows no failing requests or error logs, which makes it very challenging to debug.

And to reiterate, this problem did not occur on fresh install to digital ocean. And reverting to a working backup maintained the same problems. Including when making a brand new railway instance

(i work with jolly on this)

we had to migrate to digital ocean for now until this is fixed 😦

really would appreciate to be back on railway

Hello!

Can I see a link to this site that is hosted on Railway please?

https://onion-attendees-production.up.railway.app

you'll the top left counter is "0" days and hamburger menu doesn't work on the top right

js isn't loading

same branch/commit on https://oniondao.dev < hosted on digital ocean (DNS is still updating so you might get redirection to railway in some cases)

deployed with the same dockerfile?

yup

same exact github repo with docker file in it

using DO's app platform (same as railway github deploy)

on Railway you have a custom start command, are you also using that start command on DO?

one thing i thougth the error might be was we were initially on metal servers, switched to non metal servers, but still error persisted

yes

can try without it, using bun run preview

one sec (don't think it'll change anything, but i'll try it)

when i load the Railway hosted site im seeing 3 requests for JS files that are stuck pending

well since removing the start command you are now running a dev server

yes trying to see if that forces the files to be served any better

i dont think thats the direction we want to go in

ideally would use build + start command, but just trying to get it working

happy to try whatever else

even with bun run preview it's still not loading the js files

The dockerfile uses bun, any change you are down to switch to that to Node?

would prefer not to :/

but can try for testing

yes please

i also put the start command back for you, it will be used on the next deploy you do

switching to nixpacks as builder instead of dockerfile should auto use node right?

i cannot recommend nixpacks, but i can recommend Railpack

right, but switching the builder should be enough?

or do i need to do anything else?

you would need to delete or rename the Dockerfile to switch to either nixpacks or railpack

gotcha trying now with railpack

but probably dont wanna do that since you said you have DO hooked up to the same repo?

yea but it'll just crash for now that's fine

can rollback after testing

fair enough

like i really would prefer to get railway working, much prefer you guys to DO

want to temporarily remove your bun lock file so that node and only node is used?

hmm some errors with deps one sec

whats the best way to pass in a flag for npm install step in Railpack?

need to pass in "--legacy-peer-deps"

probably with RAILPACK_INSTALL_CMD

does that go in railway.json or in railpack.json something like that?

https://railpack.com/config/file found it

its a service variable, but if you prefer putting it in a config file you could do railpack.json

deploying

what did you end up putting in the railpack.json?

interesting approach, just use what i provided haha

uh, not sure what's causing this

one sec

no dockerfile in folder if it helps

moved it out

ill have to raise this issue with railpack, but for now did you want to move back to a Dockerfile? -

FROM node:22-slim

ENV NPM_CONFIG_UPDATE_NOTIFIER=false
ENV NPM_CONFIG_FUND=false

WORKDIR /app

COPY package.json package-lock.json ./

RUN npm ci --legacy-peer-deps

COPY . ./

RUN npm run build

ENTRYPOINT ["node", "build/index.js"]

one sec, updating

updated the Dockerfile

yup yup

how was bun coping with the dep conflict?

no idea, it just handled it

didn't give errors

i blew away package lock, rebuilding

well you still need it haha

something to do with package fetch maybe?

no, its a hidden error, you are missing a package-lock.json file

oh i forgot a git add

pushing with the lock

uhhhh

maybe i need to install tailwind differently for node?

i've updated Dockerfile

gotcha one sec

looks like it's loading with js as well

so i guess bun issue somewhere?

okay the 3d onion is bouncing

we need to do one more test to rule that out

can you give me your original dockerfile?

FROM oven/bun:latest

COPY . /app

WORKDIR /app

RUN bun install

RUN bun run build

EXPOSE 4173

CMD ["bun", "run", "preview", "--host"]

this is the editted one i was trying

let me get the one earlier than this

that one is fine, i have a theory, when you where using that bun Dockerfile, you still had the railway start command set to use node, thus you built with bun, but never ran with bun, I'm going to modify that dockerfile to also run with bun

i think this was the one before i started editting:

FROM oven/bun:1.2

# Set working directory
WORKDIR /app

# Copy package files
COPY package.json ./

# Copy the original package.json back
COPY package.json ./

# Install all dependencies
RUN bun install --no-production

# Copy application code
COPY . .

# Build the application
RUN bun run build

# Expose the port
EXPOSE 3000
ENV PORT=3000
ENV HOST=0.0.0.0

# Start the application
CMD ["node", "build/index.js"]

bring your bun lockfile back and try this simple dockerfile -

FROM oven/bun:latest

WORKDIR /app

COPY package.json bun.lock ./

RUN bun install

COPY . ./

RUN bun run build

CMD ["bun", "build/index.js"]

pushing with that

one sec

"/bun.lockb": not found

there is a bun.lock

newer version of bun

oh i'll update docker file to bun.lock

one sec

ah text based lock file, i've also updated the Dockerfile

also, pro tip, click the view in context button

bun install couldn't be found???

in the bun dockerfile???

lol what

oh it's something to do with three-perf?

what is three-perf?

no idea

it's not even in deps

its' in lockfile

looks like threlte uses it?

not sure why it's failling to clone now but was working before?

we love when packages run git clones, the node ecosystem is lovely

hahahahaha i've been in cargo hell too

the only savior is go

is there any reason git clone would be failing in this dockerfile?

oh maybe i need to add git in the dockerfile?

i dont think so, i say just try to redeploy

same error 😦

was worth a shot

back to node it is

this file right?

yeah

building

good old node

cool working, i'll move the domain over

fwiw, we have two other services running with bun with no issue (back end services though)

also this was working fine for a long time

like we had the front end service running with bun up til yesterday when it suddenly stopped serving files

i think you had it running with node technically, given your start command

oh true, but like we didn't change the start command

it was building everything with bun

just using node in the start command to serve the built files

bun is a mystery

anyway i'll move the domain over and just use node

thanks

sounds good, glad i could help

i am also curious why DO wasn't having this problem

if it was a bun issue

cause it built from the same dockerfile

shrug

diffrent container runtime?, who really knows

I believe it's a debug tool buried within the threejs package

interesting