Deploy: Christmas time release #606
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
i found that default authentication route should be `/api/auth/local`
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Signed-off-by: harimkims <harimkims@gmail.com> Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
I found that default route user register in v4 is `api/auth/local/register` Co-authored-by: DMehaffy <derrickmehaffy@gmail.com> Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Signed-off-by: harimkims <harimkims@gmail.com> Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
In the documentation about the connection parameters, the `username` parameter does not actually exist. This is probably a typo and should be replaced by the `user` parameter as per the example given below on the same page. Co-authored-by: DMehaffy <derrickmehaffy@gmail.com> Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Update default MySQL Port in example to 3306 Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
- bump MyQL/MariaDB Minimum Version for `JSON` datatype support
There should be two enclosing parenthesis at the end. Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
There are still some references to the v3 auth endpoints (without `/api` at the start) on the Users and Permissions plugin documentation. # What does it do? Updates Strapi endpoints to include `/api` at the start # Why is it needed? This change should be documented; it caused a lot of confusion for me as I was trying to figure out why my authentication was not working on v4. # Related issue(s)/PR(s) A similar thing was fixed for the guides in PR #553 Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> Co-authored-by: DMehaffy <derrickmehaffy@gmail.com>
* lifecycles.js file is not generated automatically I think since version 4, the lifecycles.js file is not created automatically but needs to be created manually, if needed. Postscript Correct me if I'm wrong. You can also rephrase this change if it is relevant and true. Thanks * Update docs/developer-docs/latest/development/backend-customization/models.md Co-authored-by: DMehaffy <derrickmehaffy@gmail.com> * Update docs/developer-docs/latest/development/backend-customization/models.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> Co-authored-by: DMehaffy <derrickmehaffy@gmail.com> Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
* WIP rewriting REST guide * Fix example * rewrite filtering and init the other two * move to request/response instead * remove an example and fix typo * remove another example based on community feedback * add missing $and and $or * 99% finished with filtering * wip population * Try adding some GitHub Actions to check links * fix syntax error in tests file * Force working directory * change to only pull request * Fix publicationState and add field selection * Add relation population examples * Add component exmple * basic dynamic zone example, need a more complex one too Need to talk to engineering about more complex example * Finished rewriting REST docs Just need to clean up left menu * Fix broken links * Fix missing commas in examples * Fix all non-uniform uses of `// ...` Yes I was bored af * fix example response syntax error * Fix extra data comments * remove workflow from this PR move to #574 * pr feedback 1 * Update docs/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Apply suggestions from code review Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/developer-resources/database-apis-reference/rest-api.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/developer-resources/database-apis-reference/rest/populating-fields.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/developer-resources/database-apis-reference/rest/populating-fields.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/developer-resources/database-apis-reference/rest/populating-fields.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * Update docs/developer-docs/latest/developer-resources/database-apis-reference/rest/populating-fields.md Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com> * tweak menu + other fixes Co-authored-by: Pierre Wizla <pwizla@users.noreply.github.com>
The default structure provided in the doc doesn't work on AWS. The provided syntax which has connection object within connection object which consists of configurations seems to work. username key is being replaced with user
|
This pull request is being automatically deployed with Vercel (learn more). documentation – ./docs🔍 Inspect: https://vercel.com/strapijs/documentation/H7XbeXNER9M47ve5jaY6aRZX2g37 |
kasonde
approved these changes
Dec 20, 2021
docs/developer-docs/latest/developer-resources/content-api/integrations/next-js.md
Show resolved
Hide resolved
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
17 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Still no change-log, sorry, read the commits