4 months ago
The "pgvector" template (https://railway.com/deploy/3jJFCA) does a couple of things that I believe are outdated:
A) It uses the prefix postgres:// instead of postgresql:// which is inconsistent with the main Postgres template and also breaks the SQLAlchemy Python package which expects postgresql:// as far as I can tell.
B) The DATABASE_URL variable is the public URL whereas the main Postgres template has this as the private URL (and then has DATABASE_URL_PUBLIC as a different variable). The pgvector template does have DATABASE_URL_PRIVATE but I think it would be best to update and align to what the main Postgres image does to allow easily switching when your app starts needing the pgvector extension.
See this Stackoverflow thread for a note on the deprecation of postgres://:
0 Threads mention this feature
0 Replies