a year ago
I am getting this error because it seems that the RONIN_TOKEN is not being injected properly or something
this happened after recent change to railway
dockerfile: https://github.com/nikitavoloboev/drophunt/blob/main/docker/api/Dockerfile
34 Replies
a year ago
a year ago
after this
a year ago
the token is valid, i double checked it
a year ago
as test I tried to do RUN echo $RONIN_TOKEN
a year ago
and see no value for it
a year ago
railway stopped injected the token
a year ago

a year ago
yes the token is just not passed 😐
a year ago
RUN bunx ronin login && bun install --production
a year ago
im doing this
a year ago
but RONIN_TOKEN is not injected
a year ago
or rather
a year ago

a year ago
how can I pass variable to the dockerfile?
a year ago

a year ago
perhaps @Brody knows
a year ago
for some reason docker builds just stopped working for me
a year ago
and now token is not being injected at all
a year ago
you answered this yourself
a year ago
this is the answer, as shown in that screenshot
a year ago
respectfully, let's try not to blame railway for everything right from the start
a year ago
oh true
a year ago
this worked
a year ago
yea was not really blaming it was just an assumption as things worked
a year ago
then suddenly stopped when i made no changes on my side I think and I remember you said there was some update being released
a year ago
won't blame again 🙂
a year ago
im new to railway and devops
a year ago
mostly worked with cloudflare workers only
a year ago
There are definitely plenty of times where it can be railway, even though I suspected it could have been railway when your application wasn't responding and was wrong, it's challenging to differentiate sometimes so no worries
a year ago
and railway is mucher nicer as there are no limitations
a year ago
was trying to pick this as answer
a year ago
and failed
a year ago

a year ago
users are not permitted to use that feature