-
Notifications
You must be signed in to change notification settings - Fork 410
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add release blog post for FerretDB v1.22.0 #4401
Conversation
Marketing blog posts should be reviewed by @ptrfarkas and @AlekSi. |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #4401 +/- ##
==========================================
+ Coverage 73.93% 74.03% +0.09%
==========================================
Files 323 323
Lines 22398 22398
==========================================
+ Hits 16561 16582 +21
+ Misses 4620 4607 -13
+ Partials 1217 1209 -8 see 10 files with indirect coverage changes
Flags with carried forward coverage won't be shown. Click here to find out more. |
Here's how you can do it: | ||
|
||
```sh | ||
ferretdb --test-enable-new-auth=true --setup-timeout=1m --setup-username=user --setup-password=pass --setup-database=ferretdb |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's drop timeout for simplicity; the default (30s) is good enough
- `--setup-username`/`FERRETDB_SETUP_USERNAME`: Specifies the username to be created. | ||
- `--setup-password`/`FERRETDB_SETUP_PASSWORD`: Specifies the password for the user (can be empty). | ||
- `--setup-timeout`/`FERRETDB_SETUP_TIMEOUT`: Sets the timeout for establishing a working backend connection. | ||
- `--setup-database`/`FERRETDB_SETUP_DATABASE`: Specifies the database to create the user in. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Let's say initial database that will be created.
(because that user is not created in this database, but in the admin
database for that setup)
- `--setup-database`/`FERRETDB_SETUP_DATABASE`: Specifies the database to create the user in. | ||
- `--test-enable-new-auth`/`FERRETDB_TEST_ENABLE_NEW_AUTH`: Must be set to `true` to enable the new authentication setup. | ||
|
||
Once the flags/environment variables are passed, FerretDB will create the specified user with the given password. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
and the given database
- `--setup-database`/`FERRETDB_SETUP_DATABASE`: Specifies the initial database that will be created. | ||
- `--test-enable-new-auth`/`FERRETDB_TEST_ENABLE_NEW_AUTH`: Must be set to `true` to enable the new authentication setup. | ||
|
||
Once the flags/environment variables are passed, FerretDB will create the specified user with the given password and database. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It does not create a user with a given [...] database
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So something like this: Once the flags/environment variables are passed, FerretDB will create the specified user with the given password and the given database.
?
Description
Readiness checklist
task all
, and it passed.@FerretDB/core
), Milestone (Next
), Labels, Project and project's Sprint fields.