Skip to content
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

Moved the "Running OpenFGA in prod" to the best practices section #996

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

aaguiarz
Copy link
Member

@aaguiarz aaguiarz commented Mar 31, 2025

Description

We moved
https://openfga.dev/docs/getting-started/running-in-production to
https://openfga.dev/docs/best-practices/running-in-production. We'd need to redirect in Cloudflare.

References

Review Checklist

  • I have clicked on "allow edits by maintainers".
  • I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
  • The correct base branch is being used, if not main
  • I have added tests to validate that the change in functionality is working as expected

@aaguiarz aaguiarz requested review from a team as code owners March 31, 2025 14:14
@aaguiarz aaguiarz requested a review from Copilot March 31, 2025 14:14
Copy link

@Copilot Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull Request Overview

This PR moves the "Production Best Practices" content to a new location under the Best Practices section, updating titles, link paths, and sidebar references accordingly.

  • Updated configuration page link and ID to point to the new best practices location.
  • Removed legacy production best practices documentation from getting-started and added a new entry under Best Practices in the sidebar and README.

Reviewed Changes

Copilot reviewed 3 out of 12 changed files in this pull request and generated no comments.

File Description
scripts/update-config-page.mjs Updated title, link, and id for the production best practices page.
docs/sidebars.js Adjusted sidebar items to remove the legacy entry and add the new link.
docs/README.md Removed old production best practices link and added new Best Practices entries.
Files not reviewed (9)
  • docs/content/best-practices/adoption-patterns.mdx: Language not supported
  • docs/content/best-practices/overview.mdx: Language not supported
  • docs/content/best-practices/running-in-production.mdx: Language not supported
  • docs/content/getting-started/overview.mdx: Language not supported
  • docs/content/getting-started/setup-openfga/access-control.mdx: Language not supported
  • docs/content/getting-started/setup-openfga/configuration.mdx: Language not supported
  • docs/content/getting-started/setup-openfga/configure-openfga.mdx: Language not supported
  • docs/content/getting-started/setup-openfga/docker-setup.mdx: Language not supported
  • docs/content/getting-started/setup-sdk-client.mdx: Language not supported
Comments suppressed due to low confidence (3)

scripts/update-config-page.mjs:234

  • Please verify that the updated relative link correctly points to the best practices page in the new folder structure.
link: './../../best-practices/running-in-production',

docs/sidebars.js:406

  • [nitpick] Consider if the label should emphasize best practices more directly (e.g., 'OpenFGA Production Best Practices') to align with documentation terminology.
label: 'Running OpenFGA in Production',

docs/README.md:81

  • Verify that the referenced document './content/best-practices/running-in-production.mdx' exists and is correctly integrated into the documentation structure.
- [Running OpenFGA in Production](./content/best-practices/running-in-production.mdx)

@aaguiarz aaguiarz changed the title Moved the "unning OpenFGA in prod" to the best practices section Moved the "Running OpenFGA in prod" to the best practices section Mar 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant