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
The current documentation lacks information in several areas:
Schema Migrations: There is no mention of how to manage schema migrations for Fly Postgres. This is an essential aspect of database management and should be addressed to help users maintain and update their database schemas effectively.
ORM Tools: There is no mention of how to interact with common ORM tools like Drizzle or Prisma. These tools are widely used by developers to simplify database interactions, and guidance on their integration with Fly Postgres would be extremely helpful.
Continuous Integration (CI): There is no mention or guidance on setting up CI for projects using Fly Postgres. CI is a vital practice for maintaining code quality and deployment reliability, and including this information would assist developers in setting up robust development workflows.
Additional info
Providing detailed sections or dedicated guides on the above topics would greatly enhance the utility of the documentation. Including examples, best practices, and common pitfalls would also be beneficial.
The text was updated successfully, but these errors were encountered:
I found an issue with this document.
Title: Managing Fly Postgres
Location: https://fly.io/docs/postgres/managing/
Source: https://github.com/superfly/docs/blob/main/postgres/managing.html.markerb
Describe the issue
The current documentation lacks information in several areas:
Schema Migrations: There is no mention of how to manage schema migrations for Fly Postgres. This is an essential aspect of database management and should be addressed to help users maintain and update their database schemas effectively.
ORM Tools: There is no mention of how to interact with common ORM tools like Drizzle or Prisma. These tools are widely used by developers to simplify database interactions, and guidance on their integration with Fly Postgres would be extremely helpful.
Continuous Integration (CI): There is no mention or guidance on setting up CI for projects using Fly Postgres. CI is a vital practice for maintaining code quality and deployment reliability, and including this information would assist developers in setting up robust development workflows.
Additional info
Providing detailed sections or dedicated guides on the above topics would greatly enhance the utility of the documentation. Including examples, best practices, and common pitfalls would also be beneficial.
The text was updated successfully, but these errors were encountered: