Weird issue with a specific route in my node.js application ONLY after deploying
I have a /get-translation route in my app. In development it works totally fine with no issues. After deploying to Railway that specific route fails to look up its corresponding views ejs file. I'm new to Railway, is there something I'm missing?
All the other routes or redirects of those routes work just fine.
Solution:Jump to solution
can you make sure the files and folders have the correct case on github as opposed to your local project?
16 Replies
Project ID:
bc58e304-a9cd-42c1-a6b9-2b614b792145project ID: bc58e304-a9cd-42c1-a6b9-2b614b792145
Any errors in the console when you go to the domain?
if possible, could you send the domain?
Failed to lookup view "../views/translator/allTranslations.ejs" in views directory "/app/views"
now this's weird because my structure doesnt have an "app" folder
nixpacks puts your project into an
/app folderahh i see
but that shouldn't matter, you are using relative paths
Solution
can you make sure the files and folders have the correct case on github as opposed to your local project?
let me check
for some reason github does not track file casing changes by default
oh i think you're right
why doesnt github track that?
no clue tbh
but you can change it
git config core.ignorecase falsewill definitely do that
thanks a lot i appreciate it :)
no problem, let me know if that solves it!
will do! trying it right now
it works!
i thought the days of errors caused by mispellings were behind me
apparently not
haha now it's errors caused by case sensitivity
but glad this is solved