Your Package Repo

A look inside: exploring package content gemfury.com/blog/2016/pack…

Happy 30 years of Ruby! The language, ecosystem, and community have had a lasting influence on how we built @Gemfury. #rubyrelease30th #ruby4

An AWS incident is causing some issues including our inability to update the status page health.aws.amazon.com/health/status?…

Our most scenic stop on the way to #RubyKaigi2025

@othello We’re on it. Please check your email.

@Gemfury getting no response from multiple support requests (trying to access an account I’m locked out of). Is anyone there?

@george_kettle We suspect an authentication issue here. If Bundler does not auth correctly to Gemfury, it will query your public repo, rather than your private one, resulting in “not found” errors for private gems.

Currently having an issue with @Gemfury when pushing to Heroku. The logs say that version 0.1.4 doesn't exist. However, the gem version does exist in Gemfury, and running bundle does work locally. So it doesn't really make sense to me? Any ideas?

@Control_Alt_Dev @jarredsumner We’ve done some quick tests and put together an initial guide. Please let us know if it works for you. gemfury.com/guide/javascri…

@jarredsumner @Gemfury yes! have tried all combinations from that page as well have reached out to @Gemfury asking they test it, figure it out, and add an example in addition to their yarn/npm instructions because it might be on their end as well (although if they are compatible with npmrc...)

@Gemfury impossible to get `bun install` to work with the private registry. Somehow something is different about your setup? which makes the npm and yarn configuration advice useless.

@galtzo Still under active development, but have been quiet recently due a sizable backend migration. Bundler has seen bugs recently in their marshaling code, which version is manifesting issues for you? Please email us, and about the other issues too - we’ll take a look.

Gemfury turns 10! fury.blog/blog/2022/10th…

@ianelantzy We are fixing this. Incident report coming.

@venriq We are fixing this. Incident report coming.

@Gemfury service looks to be down. I'm not able to upload gems through their UI or list the previously uploaded gems. Any help???

@leopard_me Thanks for catching this. Yes, we misconfigured our nameservers for “fury.blog”, but now it is fixed. If you’re still seeing errors, you may need to clear your DNS cache.

@Gemfury you main page cannot load some JS/CSS/assets files. Looks like "fury.blog" domain is not resolve anything (wait for several hours, but looks like nobody noticed this issue)

@rhymiz We’ve deployed a bug that rejected packages with larger metadata. This is fixed now.

@Gemfury push.fury.io is bombing pretty hard right now... don't see anything on your status page, though. Just a blip?

@collimarco We do some caching and so does @github. Looks like in this case, the old image is being held by GitHub’s CDN.

@Gemfury Why the gem version displayed is still 1.3 instead of 1.7 after several days? github.com/cuber-cloud/cu…

@BrendaS94595953 We’re on it. Please check your email & account.

@Gemfury just updated my card on file for Mindbody, can support please assist? Thanks so much!

@w3guy One of our services failed over, so there was a brief spike in errors. Sorry about that.

@rauldipeas Hmm. We’ll take a look.

@rauldipeas @RonoaldoPereira No problem. We just fixed it today.

@rauldipeas @RonoaldoPereira Thanks for the bug report. We will fix this.

@jagthedrummer Sorry about that. We have been dealing with scaling issues in the past couple of weeks. We will solve these sporadic errors soon.

@blaken Sorry about that. We have been dealing with scaling issues in the past couple of weeks. We will solve these sporadic errors soon.

@Gemfury Is your service down? I'm getting 503's on private feeds.

@Moyses_55 Sorry about that. We have been dealing with scaling issues in the past couple of weeks. We will solve these sporadic errors soon.

@Gemfury getting Service Unavailable 503 from gem.fury.io :'/