You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I used the one-click deploy on Railway and after almost a week of tinkering, got it working exactly the way I'd like. I use MongoDB Atlas and don't use any agents, or don't have much use for RAG either. I would like to keep RAG around for use on the odd occasion. I've configured all the components, including search and they all work perfectly.
In an effort to keep costs minimal, I enabled Serverless on all services and while Meilisearch sleeps quite contendly, RAG and Librechat keep each other up, even when not in use at all. A warning message on the RAG_API_URL env var on Railway's UI led me to think that using the Public Domain was to blame. So I changed it to Private Domain and the file upload refused to work. So now, I'm back to a fully functional set up, but one which won't sleep, because there's always some egress/ingress between the two services.
How to manage this? Would it be possible to sleep RAG API until a file upload button is selected/clicked? Might help save costs. Thank you!
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I used the one-click deploy on Railway and after almost a week of tinkering, got it working exactly the way I'd like. I use MongoDB Atlas and don't use any agents, or don't have much use for RAG either. I would like to keep RAG around for use on the odd occasion. I've configured all the components, including search and they all work perfectly.
In an effort to keep costs minimal, I enabled Serverless on all services and while Meilisearch sleeps quite contendly, RAG and Librechat keep each other up, even when not in use at all. A warning message on the RAG_API_URL env var on Railway's UI led me to think that using the Public Domain was to blame. So I changed it to Private Domain and the file upload refused to work. So now, I'm back to a fully functional set up, but one which won't sleep, because there's always some egress/ingress between the two services.
How to manage this? Would it be possible to sleep RAG API until a file upload button is selected/clicked? Might help save costs. Thank you!
Beta Was this translation helpful? Give feedback.
All reactions