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,36 +111,43 @@ 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
-
| Version | Latest Version | End-of-Life | Compatible |
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.
124
128
125
-
| Version | Latest Version | End-of-Life | Compatible |
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.
134
141
135
142
| Version | PostGIS Version | End-of-Life | Parse Server Support End | Compatible |
| Postgres 11 | 3.0, 3.1, 3.2 | November 2023 | April 2022 | ✅ Yes |
138
-
| Postgres 12 | 3.2 | November 2024 | April 2023 | ✅ Yes |
139
-
| Postgres 13 | 3.2 | November 2025 | April 2024 | ✅ Yes |
140
-
| Postgres 14 | 3.2 | November 2026 | April 2025 | ✅ Yes |
144
+
| Postgres 11 | 3.0, 3.1, 3.2 | November 2023 | April 2022 | ✅ Yes |
145
+
| Postgres 12 | 3.2 | November 2024 | April 2023 | ✅ Yes |
146
+
| Postgres 13 | 3.2 | November 2025 | April 2024 | ✅ Yes |
147
+
| Postgres 14 | 3.2 | November 2026 | April 2025 | ✅ Yes |
141
148
142
149
### Locally
150
+
143
151
```bash
144
152
$ npm install -g parse-server mongodb-runner
145
153
$ mongodb-runner start
@@ -232,7 +240,6 @@ $ curl -X GET \
232
240
}
233
241
]
234
242
}
235
-
236
243
```
237
244
238
245
To learn more about using saving and querying objects on Parse Server, check out the [Parse documentation](http://docs.parseplatform.org).
@@ -382,6 +389,7 @@ const server = ParseServer({
382
389
```
383
390
384
391
## Custom Routes
392
+
385
393
**Caution, this is an experimental feature that may not be appropriate for production.**
386
394
387
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:
@@ -414,6 +422,7 @@ The above route can be invoked by sending a `GET` request to:
414
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).
415
423
416
424
### Reserved Paths
425
+
417
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.
418
427
419
428
| Path |HTTP Method | Feature |
@@ -509,6 +518,7 @@ Identical requests are identified by their request header `X-Parse-Request-Id`.
509
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.
510
519
511
520
### Configuration example <!-- omit in toc -->
521
+
512
522
```
513
523
let api = new ParseServer({
514
524
idempotencyOptions: {
@@ -517,6 +527,7 @@ let api = new ParseServer({
517
527
}
518
528
}
519
529
```
530
+
520
531
### Parameters <!-- omit in toc -->
521
532
522
533
| Parameter | Optional | Type | Default value | Example values | Environment variable | Description |
@@ -549,6 +560,7 @@ Assuming the script above is named, `parse_idempotency_delete_expired_records.sh
549
560
## Localization
550
561
551
562
### Pages
563
+
552
564
**Caution, this is an experimental feature that may not be appropriate for production.**
553
565
554
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:
0 commit comments