From bfc85ffe69ed2ea5957146b27981b7c2472b11b1 Mon Sep 17 00:00:00 2001 From: Alexander Tobi Fashakin Date: Thu, 21 Mar 2024 15:52:02 +0100 Subject: [PATCH 1/3] Add blog post for ferretdb release v1.21 --- .../2024-03-21-new-ferretdb-v121-release.md | 59 +++++++++++++++++++ website/static/img/blog/ferretdb-v1.21.0.jpg | 3 + 2 files changed, 62 insertions(+) create mode 100644 website/blog/2024-03-21-new-ferretdb-v121-release.md create mode 100644 website/static/img/blog/ferretdb-v1.21.0.jpg diff --git a/website/blog/2024-03-21-new-ferretdb-v121-release.md b/website/blog/2024-03-21-new-ferretdb-v121-release.md new file mode 100644 index 000000000000..50d27f4138a0 --- /dev/null +++ b/website/blog/2024-03-21-new-ferretdb-v121-release.md @@ -0,0 +1,59 @@ +--- +slug: new-ferretdb-v121-release +title: FerretDB releases v1.21 with experimental support for SCRAM-SHA-1/SCRAM-SHA-256 +authors: [alex] +description: > + We have released FerretDB v1.21, and it includes experimental support for the SCRAM-SHA-1 and SCRAM-SHA-256 authentication mechanisms. +image: /img/blog/ferretdb-v1.21.0.jpg +tags: [release] +--- + +![FerretDB v1.21](/img/blog/ferretdb-v1.21.0.jpg) + +In the latest [FerretDB](https://www.ferretdb.com/) v1.21 release, we added experimental support for the `SCRAM-SHA-1`/`SCRAM-SHA-256` authentication mechanisms. + + + +This release blog post will delve into how the new authentication mechanisms work, and our ongoing efforts to improve FerretDB. + +## Experimental support for SCRAM-SHA-1/SCRAM-SHA-256 + +Earlier this year, we began work on enabling support for the `SCRAM-SHA-1` and `SCRAM-SHA-256` authentication mechanisms, and these are now available for experimental purposes. + +Enable the new authentication mode by running FerretDB with the flag `--test-enable-new-auth`/`FERRETDB_TEST_ENABLE_NEW_AUTH` environment variable. + +Once a user is created using the `createUser` command, you can use the created user credential in the connection string to connect to FerretDB. + +We encourage you to try out the new authentication mechanisms and let us know what you think. + +## Bug fixes and enhancements + +In this release, we've reorganized `upsert` handling in `update` and `findAndModify` commands, fixing an issue where filter fields were incorrectly ignored and not appended when `upsert: true`. + +In addition to that, we improved the cleanup logic for capped collections in FerretDB to correctly handle document deletion when collections are configured with a size parameter without a `max` option. + +Check out our latest [release notes for the complete list](https://github.com/FerretDB/FerretDB/releases/tag/v1.21.0) of changes in this release. + +## FerretDB v2.0: it's coming! + +Almost a year ago, we released FerretDB 1.0 GA as the first open source alternative to MongoDB, based on Postgres. +Our aim with 1.x was twofold: first, we wanted to provide a production-ready alternative to encourage the open source community to try FerretDB and provide feedback for us on their experience across a variety of different use cases and platforms. +Today, with thousands of running FerretDB around the world, we are able to understand better what the expectations are. +Your feedback, contributions and telemetry data helped us to fine-tune our roadmap. + +While we continued working on FerretDB 1.x releases, but in the background, we also turned our attention to addressing the elephant in the room: performance. + +The latest release is going to be one of the last releases of FerretDB v1.x. +FerretDB v2.0 is just around the corner, with drastically improved performance and compatibility. +FerretDB 2.0 will be a departure from our current architecture, which enables us to roll out these enhancements. + +We understand the need to make it easy for users to switch by offering a truly open source alternative that is compatible with many of their existing needs. + +So we believe FerretDB v2.0 should perform even better, enable even greater scalability and compatibility to support more application use cases. + +We hope to have it available for our users very soon. + +The open source community plays an integral role in everything we do at FerretDB, and we appreciate all the support from everyone, including partners, code contributors, and well-wishers. +Particularly for this release, we are grateful to [@farit2000](https://github.com/farit2000), [@sbshah97](https://github.com/sbshah97) as first-time contributors to FerretDB. + +If you have any question at all about FerretDB, please feel free to [reach out on any of our channels here](https://docs.ferretdb.io/#community). diff --git a/website/static/img/blog/ferretdb-v1.21.0.jpg b/website/static/img/blog/ferretdb-v1.21.0.jpg new file mode 100644 index 000000000000..049a3ba0f6b4 --- /dev/null +++ b/website/static/img/blog/ferretdb-v1.21.0.jpg @@ -0,0 +1,3 @@ +version https://git-lfs.github.com/spec/v1 +oid sha256:03c84637e549c6f5fac8e31b916a018cb22b49b8a089a9beab32fc405445fd07 +size 59614 From 195c193d401565adf45612dc94aaa2ff17709ee2 Mon Sep 17 00:00:00 2001 From: Alexander Tobi Fashakin Date: Thu, 21 Mar 2024 15:55:08 +0100 Subject: [PATCH 2/3] update post --- website/blog/2024-03-21-new-ferretdb-v121-release.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/blog/2024-03-21-new-ferretdb-v121-release.md b/website/blog/2024-03-21-new-ferretdb-v121-release.md index 50d27f4138a0..be6ace93ed37 100644 --- a/website/blog/2024-03-21-new-ferretdb-v121-release.md +++ b/website/blog/2024-03-21-new-ferretdb-v121-release.md @@ -16,7 +16,7 @@ In the latest [FerretDB](https://www.ferretdb.com/) v1.21 release, we added expe This release blog post will delve into how the new authentication mechanisms work, and our ongoing efforts to improve FerretDB. -## Experimental support for SCRAM-SHA-1/SCRAM-SHA-256 +## Experimental support for `SCRAM-SHA-1`/`SCRAM-SHA-256` Earlier this year, we began work on enabling support for the `SCRAM-SHA-1` and `SCRAM-SHA-256` authentication mechanisms, and these are now available for experimental purposes. From 042fead964449e87dba04d1e8a6ed48188138976 Mon Sep 17 00:00:00 2001 From: Alexey Palazhchenko Date: Thu, 21 Mar 2024 22:50:44 +0400 Subject: [PATCH 3/3] Update wording --- .../2024-03-21-new-ferretdb-v121-release.md | 29 +++++++++---------- 1 file changed, 14 insertions(+), 15 deletions(-) diff --git a/website/blog/2024-03-21-new-ferretdb-v121-release.md b/website/blog/2024-03-21-new-ferretdb-v121-release.md index be6ace93ed37..59349ade98c6 100644 --- a/website/blog/2024-03-21-new-ferretdb-v121-release.md +++ b/website/blog/2024-03-21-new-ferretdb-v121-release.md @@ -3,7 +3,7 @@ slug: new-ferretdb-v121-release title: FerretDB releases v1.21 with experimental support for SCRAM-SHA-1/SCRAM-SHA-256 authors: [alex] description: > - We have released FerretDB v1.21, and it includes experimental support for the SCRAM-SHA-1 and SCRAM-SHA-256 authentication mechanisms. + We have released FerretDB v1.21, which includes experimental support for the SCRAM-SHA-1 and SCRAM-SHA-256 authentication mechanisms. image: /img/blog/ferretdb-v1.21.0.jpg tags: [release] --- @@ -14,17 +14,16 @@ In the latest [FerretDB](https://www.ferretdb.com/) v1.21 release, we added expe -This release blog post will delve into how the new authentication mechanisms work, and our ongoing efforts to improve FerretDB. +This release blog post will delve into how the new authentication mechanisms work and discuss our ongoing efforts to improve FerretDB. ## Experimental support for `SCRAM-SHA-1`/`SCRAM-SHA-256` -Earlier this year, we began work on enabling support for the `SCRAM-SHA-1` and `SCRAM-SHA-256` authentication mechanisms, and these are now available for experimental purposes. - +Earlier this year, we began work on enabling support for the `SCRAM-SHA-1` and `SCRAM-SHA-256` authentication mechanisms, which are now available for experimental purposes. Enable the new authentication mode by running FerretDB with the flag `--test-enable-new-auth`/`FERRETDB_TEST_ENABLE_NEW_AUTH` environment variable. -Once a user is created using the `createUser` command, you can use the created user credential in the connection string to connect to FerretDB. +Once a user is created using the `createUser` command, you can use the created user credentials in the connection string to connect to FerretDB. -We encourage you to try out the new authentication mechanisms and let us know what you think. +We encourage you to try the new authentication mechanisms and let us know your thoughts. ## Bug fixes and enhancements @@ -36,24 +35,24 @@ Check out our latest [release notes for the complete list](https://github.com/Fe ## FerretDB v2.0: it's coming! -Almost a year ago, we released FerretDB 1.0 GA as the first open source alternative to MongoDB, based on Postgres. -Our aim with 1.x was twofold: first, we wanted to provide a production-ready alternative to encourage the open source community to try FerretDB and provide feedback for us on their experience across a variety of different use cases and platforms. +We released FerretDB 1.0 GA almost a year ago as the first open-source alternative to MongoDB, based on Postgres. +Our aim with 1.x was twofold. +First, we wanted to provide a production-ready alternative to encourage the open-source community to try FerretDB. +Second, we wanted to get feedback on experience across a variety of different use cases and platforms. Today, with thousands of running FerretDB around the world, we are able to understand better what the expectations are. -Your feedback, contributions and telemetry data helped us to fine-tune our roadmap. +Your feedback, contributions, and telemetry data helped us to fine-tune our roadmap. -While we continued working on FerretDB 1.x releases, but in the background, we also turned our attention to addressing the elephant in the room: performance. +While we continued working on FerretDB 1.x releases, in the background, we also turned our attention to addressing the elephant in the room: performance. The latest release is going to be one of the last releases of FerretDB v1.x. FerretDB v2.0 is just around the corner, with drastically improved performance and compatibility. FerretDB 2.0 will be a departure from our current architecture, which enables us to roll out these enhancements. -We understand the need to make it easy for users to switch by offering a truly open source alternative that is compatible with many of their existing needs. - -So we believe FerretDB v2.0 should perform even better, enable even greater scalability and compatibility to support more application use cases. - +We understand the need to make it easy for users to switch by offering a truly open-source alternative that is compatible with many of their existing needs. +We believe FerretDB v2.0 should perform even better and enable even greater scalability and compatibility to support more application use cases. We hope to have it available for our users very soon. The open source community plays an integral role in everything we do at FerretDB, and we appreciate all the support from everyone, including partners, code contributors, and well-wishers. Particularly for this release, we are grateful to [@farit2000](https://github.com/farit2000), [@sbshah97](https://github.com/sbshah97) as first-time contributors to FerretDB. -If you have any question at all about FerretDB, please feel free to [reach out on any of our channels here](https://docs.ferretdb.io/#community). +If you have any questions about FerretDB, please feel free to [reach out on any of our channels here](https://docs.ferretdb.io/#community).