wfarr

8 ms·

1.
by wfarr 14y ago
The status site now handles both HTTP and HTTPS gracefully.
2.
by wfarr 14y ago
The status site now supports SSL and auto-redirects regular HTTP traffic to HTTPs.
3.
by wfarr 14y ago
Yes.
4.
by wfarr 14y ago
In fact, all HTTP access redirects to HTTPS for just about everything. And most modern browsers (recent versions of Chrome and Safari) that have accessed a website over HTTPS once happen to _prefer_ HTTPS by default for that site.
5.
by wfarr 14y ago
> github's "copy url" bit! That's entirely a limitation imposed by JavaScript not supporting keyboard access. We'd rather not rely on Flash, but we have to in this case.
6.
by wfarr 14y ago
> They are shipping a completely outdated GCC They are shipping a heavily modified GCC that originally was forked in 2008. The version of GCC they ship is entirely based on LLVM via Clang and is intended to be a hold-over for everything
7.
by wfarr 14y ago
Never on iOS though. Most of the features Google added to the Android version of Maps never made it to iOS, for whatever reason (be it Apple not allowing it or Google decided they didn't want to).
8.
by wfarr 14y ago
At the time of the outage, the status site was seeing upwards of 30,000/req minute. AS we scaled up dynos, we would see temporary performance improvements until the status site would stop responding again. In the short term, this led to us
9.
by wfarr 14y ago
It's a fairly recent addition to git (January 2012). You need at least version 1.7.9 to use credential caching. [1] [1]: http://git-blame.blogspot.com/2012/01/git-179.html
10.
by wfarr 14y ago
Is that even relevant when Apple is taking home the biggest slice of the profit pie?
11.
by wfarr 14y ago
Not to mention, the glaring problem people like to ignore when discussing this is the motherboard in the MBP is only going to support so much memory anyway (would not be surprised if it could only support 16gb), so talking about not being a
12.
by wfarr 15y ago
Having worked with some quite large Mongo setups, I think you'll find the administration of Mongo ends up being significantly more than a single upfront cost. Dealing with sharding + replica sets is an administrative nightmare with Mongo.
13.
by wfarr 15y ago
You might be interested in https://github.com/paperlesspost/graphiti It's somewhat based on some of the stuff Github uses internall for graph generation (so the README says).
14.
by wfarr 15y ago
Certainly a LOT of it is rspec 2.8. But there was a definite increase with Rails 2.3 as well. :)
15.
by wfarr 15y ago
Seeing about 25% speedup here with just the Rails 3.2 RC1. Combined with rspec-rails 2.8.0.rc2 (which includes some Rails 3.2-related changes), I saw my test suite go from ~2.5s (Rails 3.2.0.rc1 w/ rspec 2.7.x) to ~0.43s (Rails 3.2.0.rc1 w/
16.
by wfarr 15y ago
Except the part where people who received the original email have 100% control over whether or not they do tell other people about it.
17.
by wfarr 15y ago
> PLEASE DO NOT REPUBLISH THIS INFORMATION! From the linked email.
18.
GitHub: Recent Load Balancer Problems (RCA)(github.com)
58 points by wfarr 15y ago|9 comments
19.
by wfarr 15y ago
This removes discoverability of what could be useful (if small) gems. At the very least, these could be made into full repos on GitHub with READMEs so they're relatively easy to find between GitHub's own search and Google.
20.
by wfarr 15y ago
I hope this is some sort of staging or testing server? The idea of repeatedly writing code and rsyncing it up to a production server while adding new features/whatever seems incredibly error prone to me. And that's not even to touch on whet
21.
by wfarr 15y ago
That's what the bookmark system is there for.
22.
by wfarr 15y ago
It's not a matter of SQL vs. NoSQL. They are complementary. The fact of the matter is, there are some components of systems for which Redis, Riak, etc may be better suited than SQL in the long term. Starting out, keeping everything in SQL p
23.
by wfarr 15y ago
DP4 was also likely tagged at least a month before its release to developers. Their DP releases aren't current. They're older, generally more stable snapshots. EDIT: This means that they've been improving stability long since the last DP, a
24.
by wfarr 15y ago
"Over the next couple of years a lot of developers are going to make good money moving companies off of Node.js and MongoDB." - http://twitter.com/#!/b6n/status/73535660467818496
25.
by wfarr 15y ago
https://github.com/lsegal
26.
by wfarr 15y ago
It was forked because while performance improvements are great to have, API breakage with no replacement for long-standing APIs is not. At the end of the day, people need a working environment and not everyone has the time of day to be upda
27.
by wfarr 16y ago
Given that, I'd definitely recommend you check out Rump: https://github.com/railsmachine/rump It'll let you manage your servers in a headless manner, using simple version control via git to manage your puppet configuration. [Disclaimer: I
28.
by wfarr 16y ago
You may be interested in checking out Rump: https://github.com/railsmachine/rump [Disclaimer: I work for Rails Machine.] It's essentially a headless puppet that centers around a workflow of testing changes from an individual checkout of t
29.
by wfarr 16y ago
That is frustrating. :(
30.
by wfarr 16y ago
What release are you using and on what OS? I'm running '11.0.672.2 dev' on OS X and don't see such an option.

More ›