docs: Managed Postgres callout + optional Appwrite link on postgres.mdx?

Open Beginner friendly
#843 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
1/5
Estimated time
1-3 hours
Newbie friendliness
74/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Active
Tech stack
postgresql
Domain
databases, documentation

Research direction

Open docs/databases/postgres.mdx and read the top section and Connection Options area to choose the placement for a short managed PostgreSQL callout. Confirm whether the Appwrite link is approved or should be omitted, then ensure the finished page explains hosted Postgres compatibility and the typical SSL requirement.

Written by the indexing model from the issue text.

Description

Proposal

Would the maintainers be open to a small “Managed Postgres” callout on docs/databases/postgres.mdx?

Many users connect Sequelize to hosted Postgres (Neon, Supabase, Appwrite, RDS, etc.) with the standard @sequelize/postgres dialect. A short tip that SSL is typically required (ssl: true / sslmode=require) plus an optional link to a vendor guide can save folks from connection failures without inventing per-vendor dialect pages.

Suggested addition (sketch)

Something brief near the top of the PostgreSQL page or under Connection Options, for example:

Managed PostgreSQL: Hosted providers that speak standard Postgres work with @sequelize/postgres. Enable SSL (ssl: true). See Appwrite’s Sequelize guide for a worked example (guide may be publishing shortly; canonical URL).

I’m happy to open a tiny PR if this direction is welcome, or to omit the vendor link and only keep a generic SSL / managed-host tip if you prefer no outbound vendor links.

Disclosure

I’m Jake Barnby (@abnegate) and I work at Appwrite. Not asking for a large docs redesign — just checking whether a short callout is acceptable before sending a PR.

Thanks!

Dominant language
HTML
Stars
30
Forks
170
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from sequelize/website

All issues in sequelize/website

Similar issues

More Databases issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.