chartdb semicolon injection when building
xdnlor
HOBBYOP

a year ago

production-id: a4fd30df-4dba-4cfb-bf5a-740b136b74f8

when setting the necessary variables to use chartdb's ai features, railway seems to inject a semicolon into the build log.

build-log when no variable is set within Railway:

"[builder 6/7] RUN echo "VITE_OPENAI_API_KEY=${VITE_OPENAI_API_KEY}" > .env && echo "VITE_OPENAI_API_ENDPOINT=${VITE_OPENAI_API_ENDPOINT}" >> .env && echo "VITE_LLM_MODEL_NAME=${VITE_LLM_MODEL_NAME}" >> .env && echo "VITE_HIDE_BUCKLE_DOT_DEV=${VITE_HIDE_BUCKLE_DOT_DEV}" >> .env".

build log when variable VITE_OPENAI_API_ENDPOINT="hxxxs://openrouter.ai/api/v1" (no semicolon) is set on Railway

the build log looks like this: "[builder 6/7] RUN echo "VITE_OPENAI_API_KEY=${VITE_OPENAI_API_KEY}" > .env && echo "VITE_OPENAI_API_ENDPOINT=hxxx://openrouter.ai/api/v1"; >> .env && echo "VITE_LLM_MODEL_NAME=${VITE_LLM_MODEL_NAME}" >> .env && echo "VITE_HIDE_BUCKLE_DOT_DEV=${VITE_HIDE_BUCKLE_DOT_DEV}" >> .env"

chartdb docker file: https://github.com/chartdb/chartdb/blob/main/Dockerfile

thx!

2 Replies

a year ago

why are you doing line 16


xdnlor
HOBBYOP

a year ago

just the offical chartdb docker file, I guess you mean that it's unnecessary to write the values into a .env file at build time since railway is supplying them at runtime anyway?


Welcome!

Sign in to your Railway account to join the conversation.

Loading...