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

Adds persistence link to cluster status #1480

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

ZPain8464
Copy link
Contributor

@ZPain8464 ZPain8464 requested a review from gaurdro June 26, 2024 22:23
@ZPain8464 ZPain8464 requested a review from a team as a code owner June 26, 2024 22:23
@ZPain8464 ZPain8464 requested review from cmo-pomerium and removed request for a team June 26, 2024 22:23
Copy link

netlify bot commented Jun 26, 2024

Deploy Preview for pomerium-docs ready!

Name Link
🔨 Latest commit 3eb7b15
🔍 Latest deploy log https://app.netlify.com/sites/pomerium-docs/deploys/667c94da8cf75e0009a87691
😎 Deploy Preview https://deploy-preview-1480--pomerium-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@@ -63,7 +63,7 @@ This cluster status alert throws an error if it detects a cluster isn't connecte

By default, a cluster uses an in-memory storage backend to synchronize replicas. This does not persist your configuration. For production environments, we recommend connecting each cluster instance to its own dedicated PostgreSQL database.
Copy link
Contributor

Choose a reason for hiding this comment

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

I think I'd prefer the link to be up here, but good with either.

Suggested change
By default, a cluster uses an in-memory storage backend to synchronize replicas. This does not persist your configuration. For production environments, we recommend connecting each cluster instance to its own dedicated PostgreSQL database.
By default, a cluster uses an in-memory storage backend to synchronize replicas. This does not persist your configuration. For production environments, we recommend connecting each cluster instance to its own dedicated PostgreSQL database. Instructions on how to set this up are on the [**Persistence**](/docs/internals/data-storage#backends) page

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants