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
@@ -110,6 +111,7 @@ Before you start make sure you have installed:
110
111
### Compatibility
111
112
112
113
#### Node.js
114
+
113
115
Parse Server is continuously tested with the most recent releases of Node.js to ensure compatibility. We follow the [Node.js Long Term Support plan](https://github.com/nodejs/Release) and only test against versions that are officially supported and have not reached their end-of-life date.
114
116
115
117
| Version | Latest Version | End-of-Life | Compatible |
@@ -121,6 +123,7 @@ Parse Server is continuously tested with the most recent releases of Node.js to
121
123
| Node.js 18 | 18.1.0 | April 2025 | ✅ Yes |
122
124
123
125
#### MongoDB
126
+
124
127
Parse Server is continuously tested with the most recent releases of MongoDB to ensure compatibility. We follow the [MongoDB support schedule](https://www.mongodb.com/support-policy) and only test against versions that are officially supported and have not reached their end-of-life date.
125
128
126
129
| Version | Latest Version | End-of-Life | Compatible |
@@ -133,6 +136,7 @@ Parse Server is continuously tested with the most recent releases of MongoDB to
133
136
| MongoDB 5.2 | 5.2.1 | TBD | ✅ Yes |
134
137
135
138
#### PostgreSQL
139
+
136
140
Parse Server is continuously tested with the most recent releases of PostgreSQL and PostGIS to ensure compatibility, using [PostGIS docker images](https://registry.hub.docker.com/r/postgis/postgis/tags?page=1&ordering=last_updated). We follow the [PostgreSQL support schedule](https://www.postgresql.org/support/versioning) and [PostGIS support schedule](https://www.postgis.net/eol_policy/) and only test against versions that are officially supported and have not reached their end-of-life date. Due to the extensive PostgreSQL support duration of 5 years, Parse Server drops support if a version is older than 3.5 years and a newer version has been available for at least 2.5 years.
137
141
138
142
| Version | PostGIS Version | End-of-Life | Parse Server Support End | Compatible |
@@ -143,6 +147,7 @@ Parse Server is continuously tested with the most recent releases of PostgreSQL
143
147
| Postgres 14 | 3.2 | November 2026 | April 2025 | ✅ Yes |
144
148
145
149
### Locally
150
+
146
151
```bash
147
152
$ npm install -g parse-server mongodb-runner
148
153
$ mongodb-runner start
@@ -235,7 +240,6 @@ $ curl -X GET \
235
240
}
236
241
]
237
242
}
238
-
239
243
```
240
244
241
245
To learn more about using saving and querying objects on Parse Server, check out the [Parse documentation](http://docs.parseplatform.org).
@@ -385,6 +389,7 @@ const server = ParseServer({
385
389
```
386
390
387
391
## Custom Routes
392
+
388
393
**Caution, this is an experimental feature that may not be appropriate for production.**
389
394
390
395
Custom routes allow to build user flows with webpages, similar to the existing password reset and email verification features. Custom routes are defined with the `pages` option in the Parse Server configuration:
@@ -417,6 +422,7 @@ The above route can be invoked by sending a `GET` request to:
417
422
The `handler` receives the `request` and returns a `custom_page.html` webpage from the `pages.pagesPath` directory as response. The advantage of building a custom route this way is that it automatically makes use of Parse Server's built-in capabilities, such as [page localization](#pages) and [dynamic placeholders](#dynamic-placeholders).
418
423
419
424
### Reserved Paths
425
+
420
426
The following paths are already used by Parse Server's built-in features and are therefore not available for custom routes. Custom routes with an identical combination of`path` and `method` are ignored.
421
427
422
428
| Path |HTTP Method | Feature |
@@ -512,6 +518,7 @@ Identical requests are identified by their request header `X-Parse-Request-Id`.
512
518
Deduplication is only done for object creation and update (`POST` and `PUT` requests). Deduplication is not done for object finding and deletion (`GET` and `DELETE` requests), as these operations are already idempotent by definition.
513
519
514
520
### Configuration example <!-- omit in toc -->
521
+
515
522
```
516
523
let api = new ParseServer({
517
524
idempotencyOptions: {
@@ -520,6 +527,7 @@ let api = new ParseServer({
520
527
}
521
528
}
522
529
```
530
+
523
531
### Parameters <!-- omit in toc -->
524
532
525
533
| Parameter | Optional | Type | Default value | Example values | Environment variable | Description |
@@ -552,6 +560,7 @@ Assuming the script above is named, `parse_idempotency_delete_expired_records.sh
552
560
## Localization
553
561
554
562
### Pages
563
+
555
564
**Caution, this is an experimental feature that may not be appropriate for production.**
556
565
557
566
Custom pages as well as feature pages (e.g. password reset, email verification) can be localized with the `pages` option in the Parse Server configuration:
* interrupted WebSocket connection not closed by LiveQuery server ([#8012](https://github.com/parse-community/parse-server/issues/8012)) ([2d5221e](https://github.com/parse-community/parse-server/commit/2d5221e48012fb7781c0406d543a922d313075ea))
* align file trigger syntax with class trigger; use the new syntax `Parse.Cloud.beforeSave(Parse.File, (request) => {})`, the old syntax `Parse.Cloud.beforeSaveFile((request) => {})` has been deprecated ([#7966](https://github.com/parse-community/parse-server/issues/7966)) ([c6dcad8](https://github.com/parse-community/parse-server/commit/c6dcad8d167d44912dbd416d328519314c0809bd))
0 commit comments