Skip to content

Updates the db reference with sqlite and postgres#556

Open
BoDonkey wants to merge 1 commit into
mainfrom
update-db-documentation
Open

Updates the db reference with sqlite and postgres#556
BoDonkey wants to merge 1 commit into
mainfrom
update-db-documentation

Conversation

@BoDonkey

@BoDonkey BoDonkey commented Jul 8, 2026

Copy link
Copy Markdown
Contributor

Please indicate which branch this PR should merge into:

Check one

  • main
  • latest
  • stable
  • Check if this PR will be resubmitted against another branch

Summary

Summarize the changes briefly, including which issue/ticket this resolves. If it closes an existing Github issue, include "Closes #[issue number]"
This PR updates the @apostrophe/db reference document with the new database options. Closes PRO-9680

What are the specific steps to test this change?

For example:

  1. Run the website and log in as an admin
  2. Open a piece manager modal and select several pieces
  3. Click the "Archive" button on the top left of the manager and confirm that it should proceed
  4. Check that all pieces have been archived properly

What kind of change does this PR introduce?

(Check at least one)

  • Bug fix
  • New feature
  • Refactor
  • Documentation
  • Build-related changes
  • Other

Make sure the PR fulfills these requirements:

  • It includes a) the existing issue ID being resolved, b) a convincing reason for adding this feature, or c) a clear description of the bug it resolves
  • The changelog is updated
  • Related documentation has been updated
  • Related tests have been updated

If adding a new feature without an already open issue, it's best to open a feature request issue first and wait for approval before working on it.

Other information:

@BoDonkey BoDonkey requested a review from boutell July 8, 2026 09:39
@linear

linear Bot commented Jul 8, 2026

Copy link
Copy Markdown

PRO-9680

|`port` | Integer | A port to use in the database URI if the `uri` option is not used. This falls back to `27017`. |
|`name` | String | The project's database name. This falls back to the project [shortname](/reference/glossary.md#shortname). |
|`client` | String |An existing MongoDB connection (MongoClient) object. If present, it is used and `uri`, `host`, `connect`, etc. are ignored. |
|`uri` | String | The database connection URI. May use the `mongodb://`, `sqlite://`, or `postgres://` protocol. See the [MongoDB URI documentation](https://docs.mongodb.com/manual/reference/connection-string/) for the MongoDB format. |

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or multipostgres

Link to our documentation too

<!-- Some are used within the module and would just create noise here. -->

Because this module has an alias, you can call these from another module from the alias path. For example, `self.apos.db.connectToMongo()`.
Because this module has an alias, you can call these from another module from the alias path. For example, `self.apos.db.connectToDb()`.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this isn't new, but: this is not the case. The db module has no alias, which was called out earlier in the same document. self.apos.db is the database object.

All in all I think removing this section would be best at this point. If someone really wants to make a connection completely independent of self.apos.db they should consider using @apostrophecms/db-connect directly.

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