-
Notifications
You must be signed in to change notification settings - Fork 34
Add post about disabling locales in rubygems.org #255
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
16 changes: 16 additions & 0 deletions
16
_posts/2026-04-07-temporarily-disabling-language-support.md
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
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,16 @@ | ||||||
| --- | ||||||
| title: Temporarily disabling language support on rubygems.org | ||||||
| layout: post | ||||||
| author: Colby Swandale | ||||||
| author_email: colby@rubygems.org | ||||||
| --- | ||||||
|
|
||||||
| I'm one of the operators of [rubygems.org](https://rubygems.org). Here's what's been happening over the past week, and a temporary change we're making as a result. | ||||||
|
|
||||||
| For the past seven days, [rubygems.org](https://rubygems.org) has been under sustained bot traffic from many different sources scraping data from every published gem. The volume has been large enough to force the site offline while we respond. The bots are deliberately bypassing the Fastly cache, hitting our origin servers directly. | ||||||
|
|
||||||
| The primary target has been our language locale pages, the translated versions of [rubygems.org](https://rubygems.org). Unfortunately, the locale system wasn't designed to cache easily through a CDN. To protect site stability, we're temporarily disabling language support while we rearchitect how locale pages are cached. | ||||||
|
|
||||||
| We'll restore language support as soon as we have caching in place that can handle this volume. Thank you for your patience. | ||||||
|
|
||||||
| P.S. if you need gem and version data for a project, we publish regular database exports at <https://rubygems.org/pages/data>. We strongly recommend using those instead of scraping [rubygems.org](https://rubygems.org) directly. | ||||||
|
||||||
| P.S. if you need gem and version data for a project, we publish regular database exports at <https://rubygems.org/pages/data>. We strongly recommend using those instead of scraping [rubygems.org](https://rubygems.org) directly. | |
| P.S. If you need gem and version data for a project, we publish regular database exports at <https://rubygems.org/pages/data>. We strongly recommend using those instead of scraping [rubygems.org](https://rubygems.org) directly. |
Oops, something went wrong.
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.
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.
For consistency with existing blog posts and the site’s branding, consider capitalizing the name as “RubyGems.org” (including in the link text) instead of “rubygems.org”. For example, _posts/2018-03-09-rubygems-february-2018-updates.md uses “RubyGems.org” in both headings and body text.