11 days ago
Hello Railway Team!
Project: autonoma-app
Domain: www.autonomaapp.com.br
Problem:
The app displays "cards" of old professionals who no longer exist.
There is no static seed in the repository, and the database used is Neon (PostgreSQL) via Prisma.
Everything indicates that the app is still reading a professionals.json file within the container or from some persistent volume in Railway.
What we have already verified:
The local professionals.json file is empty.
There are no records in the Neon database (via Prisma Studio).
But old professionals still appear in the production app.
What we need to confirm:
1. Is there any volume or cache within Railway where data/professionals.json can be saved?
2. What is the correct path to safely remove it (Shell or panel)?
3. How to ensure that the app no longer reads local files (only Neon/Prisma)?
Environment:
Node.js + Express + Prisma
Neon Database (PostgreSQL)
Configured DATABASE_URL
Commands already executed in the Shell:
find / -type f -name 'profissionais.json' 2>/dev/null
ls -l /app/data
echo $DATABASE_URL
We want to completely clear the cache or local volume that may contain this file and ensure that only the Neon database can read it.
Thank you!
— Kadu Costa (Autônoma.app)
---
1 Replies
11 days ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 11 days ago
11 days ago
this data can still reside from your image (if you've mounted a volume to it), build artifacts (if it was included in your startup build), or CDN cache. you should clear your cache if you use CF, here's the docs for it. if that doesn't work, you should implement code-level changes to ensure that it's no longer there. you can check to see if the image still exists by performing a command grep -R "professionals.json" -n /app 2>/dev/null
you can redeploy a clean image, or add a no-store on responses res.set('Cache-Control','no-store'); for your dockerfile
Attachments