Agile Testing
agiletesting.blogspot.com · Personal blog · on HN since 2008
Grig Gheorghiu's blog on Python, testing, and deploying infrastructure, including Amazon EC2, load balancing, and running databases.
What HN saysHN links it for practical deployment write-ups, including EC2 experiences and push versus pull deployment systems.
18HN people shared it
2linked it in comments
18stories submitted
148story points
10 years agolast shared
2008people per year2026
Most-shared posts
- 1Automated deployment systems: push vs. pull2 people · 6 points · first shared 2010 · 2 comments on HN
- 2Deploying Tornado in production1 people · 39 points · first shared 2009 · 5 comments on HN
- 3Experiences deploying a large-scale infrastructure in Amazon EC21 people · 37 points · first shared 2009 · 4 comments on HN
- 4Load Balancing in Amazon EC2 with HAProxy1 people · 32 points · first shared 2009 · discussion on HN
- 5An ode to running a database on bare metal1 people · 5 points · first shared 2012 · 3 comments on HN
- 6The dangers of uniformity1 people · 5 points · first shared 2012 · 1 comments on HN
- 7Lessons learned from deploying a production database in EC21 people · 5 points · first shared 2011 · 1 comments on HN
- 8Easy parsing with pyparsing1 people · 3 points · first shared 2008 · discussion on HN
- 915 things I learned from "Shipping Greatness"1 people · 3 points · first shared 2012 · discussion on HN
- 10Agile Testing: Docker Orchestration with Rancher1 people · 3 points · first shared 2016 · discussion on HN
- 11Initial experiences with the Prometheus monitoring system1 people · 2 points · first shared 2015 · discussion on HN
- 12Using libcloud to manage instances across multiple cloud providers1 people · 2 points · first shared 2010 · discussion on HN
- 13How to whip your infrastructure into shape1 people · 2 points · first shared 2010 · discussion on HN
- 14Running Gatling load tests in Docker containers via Jenkins1 people · 1 points · first shared 2016 · discussion on HN
- 15Links to resources from PyCon talks1 people · 1 points · first shared 2008 · discussion on HN
What HN people wrote when they linked it
qwer · 2016-01-20
> I never understood why some people are scared of branching.
Well this is branching (in the same way that if..else is branching), just not in the VCS. What's the advantage? This methodology can allow code to go to production for some or all users, either as dark launches ( http://agiletesting.blogspot.com/2009/07/dark-launching-and-other-less… ) or as production code. VCS branching gives you none of that, and sometimes you need to roll things out sloooowly, either for quality control or for capacity monitoring.
> It seems to work pretty well for Linux development.
Well for example, if you're following the linux development model for webops, you're almost certainly doing it wrong. I'm sure your website doesn't have release candidates and LTS versions all at different URLs.
> As long as you merge continuously from upstream, you're golden.
This is not really true either. It's fine if you're the only one on a team following that model, but if everyone on your team follows that model, you're delaying collaboration and causing merge debt. Upstream ends up like a ghost town until someone like you dumps a week worth of work on it just before you're about to dump your week's worth too.
> I _do_ have some reservations against #ifdef-sprinkled code.
This is definitely a downside! You have to use a lot of discipline to keep this minimal and well-organized.
Luyt · 2011-10-20
"This address is restricted
This address uses a network port which is normally used for purposes other than Web browsing. Firefox has canceled the request for your protection.
"
This 'port banning' is described in http://www-archive.mozilla.org/projects/netlib/PortBanning.html, and the page at http://agiletesting.blogspot.com/2008/09/getting-around-firefox-port-b… describes how you can use about:config to disable the blocking:
"1) go to about:config in the Firefox address bar
2) right click, choose new->string
3) enter the name network.security.ports.banned.override and the value '1-65535' (without the quotes)
"
I tried it, and it worked: http://open.zorinaq.com:25/