Arize AI Community Icon

Home
Events

Arize AX Releases
Arize AX Support
Arize News
Arize Observe
Discussions
Introductions
Phoenix Support

Powered by Tightknit

Phoenix Support

Does PHOENIX_SQL_DATABASE_URL Replace PHOENIX_WORKING_DIR? | Arize AI Community

Phoenix Support

Does PHOENIX_SQL_DATABASE_URL Replace PHOENIX_WORKING_DIR?

·Oct 17, 2024 03:51 PM

Hi there! Quick question. If one configures PHOENIX_SQL_DATABASE_URL, will the working directory (PHOENIX_WORKING_DIR) still be used? In other words, does Phoenix still require local storage even when a database is connected?

10 comments

· Sorted by Oldest

RunLLM
APP
·
Yes, Phoenix still requires local storage even when a database is connected. The PHOENIX_WORKING_DIR is used for saving, loading, and exporting datasets, and must be accessible by both the Phoenix server and the notebook environment. This is independent of the database configuration, which is specified by PHOENIX_SQL_DATABASE_URL for logging traces and evaluations (source, source).Would you like more detail on how these configurations interact? Sources: - Server Configuration - Phoenix Config
💡 Hint: Mention RunLLM in the thread for followups.
Mikyo
·
Elliot P. good question - it doesn't really use it for much - especially for tracing. The boot time of phoenix does require it to have write access to that directory but it will largely go un-used when you use sql
Mikyo
·
in other words no need to add a persistent volume or disc for that directory if you use sql
Elliot P.
·
Thank you, Mikyo. That makes sense; in my system’s read-only environment, the server fails to load with Read-only file system: '/.phoenix'. Will enable access to a temporary directory.
Elliot P.
·
Really appreciate the help!
Roger Y.
·
yea, we should probably revisit this constraint. Would you mind opening i ticket for us to track?
Roger Y.
·
are you using postgres or sqlite?
Elliot P.
·
Thanks, Roger. I've created https://github.com/Arize-ai/phoenix/issues/5070.
Elliot P.
·
are you using postgres or sqlite?
I'm using postgres.
Roger Y.
·
thank you!