Skip to content

Conversation

@oscartobar
Copy link
Contributor

Two bugs have been fixed:

  • When the production database starts and is empty, it generates the error "index "ix_users_email" does not exist." This bug has been fixed.
  • When using the latest version of PostgreSQL (18), it generates the error /var/lib/postgresql/data Bracket Docker in Postgres 18 #1389.
    New functionality has been added:
  • New functionality has been added to allow APIs to be private, eliminating the need for CORS in production. If APIs need to be published, a parameter has been created for this purpose. See API-MODES.md

@vercel
Copy link

vercel bot commented Nov 1, 2025

@oscartobar is attempting to deploy a commit to the evroon's projects Team on Vercel.

A member of the Team first needs to authorize it.

@evroon
Copy link
Owner

evroon commented Nov 12, 2025

Thanks for the PR!

Hmm I am not really sure what the changes related to CORS attempt to solve.

Maybe the fix for postgres 18 can be a separate (smaller) PR?

When the production database starts and is empty, it generates the error "index "ix_users_email" does not exist." This bug has been fixed.

That index should be getting created once you run ./cli.py create-dev-db. Why do we need to change the alembic of (two years ago) for this and add more code in db_init.py etc.?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants