Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Issue with the "Managing Fly Postgres" doc #1636

Open
keepforever opened this issue Jul 2, 2024 · 0 comments
Open

Issue with the "Managing Fly Postgres" doc #1636

keepforever opened this issue Jul 2, 2024 · 0 comments

Comments

@keepforever
Copy link

keepforever commented Jul 2, 2024

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:

  1. 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.

  2. 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.

  3. 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.

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

No branches or pull requests

1 participant