-
Notifications
You must be signed in to change notification settings - Fork 12
Restructure Memgraph in production #1276
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
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
I am okay with this structure but I would like to keep the message how to actually read this guide. First the best practices and then the overall workloads. Because from this structure it's not clear that best practices -> specific workload is the order, which was the message I was trying to carry out for people to guide them |
Each guide has a note that Deployment best practices should be read first and Workloads page has this info as well. Do you think that’s not clear enough? |
"best-practices": "Best practices", | ||
"workloads": "Workloads", | ||
"environments": "Environments", | ||
"benchmarking-memgraph": "Benchmarking", | ||
} |
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.
newline after line 6-7
"aws": "AWS", | ||
"gcp": "GCP", | ||
"azure": "Azure" | ||
} |
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.
newline
Memgraph in production General suggestions are actually Deployment best practices we wanted to have for so long. (that's how I see it)
Then, we have suggestions based on a different workload or environment where user is deploying.
Let me know what you think of this structure.
Btw. the biggest content change is just removing emojis as we are not using them across the docs.