-
Notifications
You must be signed in to change notification settings - Fork 887
docs: scaling Coder #5550
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
docs: scaling Coder #5550
Conversation
Co-authored-by: Dean Sheather <dean@deansheather.com>
Co-authored-by: Dean Sheather <dean@deansheather.com>
Co-authored-by: Dean Sheather <dean@deansheather.com>
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.
Really nice article! Let's get this in.
I left here a few comments, but nothing to be fixed before merging. Feel free to respond and address later if you like.
docs/manifest.json
Outdated
"title": "Scaling Coder", | ||
"description": "Reference architecture and load testing tools", | ||
"icon_path": "./images/icons/scale.svg", | ||
"path": "./admin/scale/index.md" |
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.
nit: do we expect more pages or would scale.md
be sufficient?
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.
Down the road, we may provide reference architectures! I'll just make it scale.md
though
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.
LGTM! Thanks for addressing the comments.
Minimal documentation around our scale tests and how to run the
scaletest
utility against your own Coder deployment.We're considering expanding on this doc with example architecture, test results, and general recommendations around scaling out a Coder deployment.