Comments for nutrun

Comment on Hello world nginx module by Samuel

Samuel — Fri, 08 Jan 2010 06:54:37 +0000

Thanks very useFul.

Comment on Incremental deployment by George Malamidis

George Malamidis — Mon, 04 Jan 2010 12:11:27 +0000

Hi Andy,

We use a third party DNS service that load balances between AWS regions and between the AWS / “non-AWS” servers. All requests go to one domain that gets delegated internally, at DNS level, so clients only have to deal with one DNS entry that never changes.

Comment on Incremental deployment by Andrew Johnstone

Andrew Johnstone — Sat, 02 Jan 2010 13:25:46 +0000

Hi,

I’m curious to know how you handle high availability, in particular with your DNS and non AWS failover. In the event of complete failure at our current provider we can reconfigure all of our services within one hour onto EC2. However the biggest issue for us is redirecting DNS or redirecting traffic to the new servers. The clients that use our services are large corporates that cache DNS.

Cheers

Andy

Comment on Incremental deployment by volcane

volcane — Tue, 22 Dec 2009 15:43:26 +0000

Here’s something similar I came up with recently:

http://www.devco.net/archives/2009/11/06/test_driven_deployment_-_mcollective_puppet_cucumber.php

Comment on Incremental deployment by Tweets that mention Incremental deployment « nutrun -- Topsy.com

Tweets that mention Incremental deployment « nutrun -- Topsy.com — Tue, 22 Dec 2009 15:03:38 +0000

[...] This post was mentioned on Twitter by Peter Waldschmidt, George Malamidis. George Malamidis said: Me on @pingles's and @andykent's critical, high availability system deployment strategy http://bit.ly/8ZJxIz [...]

Comment on Incremental deployment by Dmytro Shteflyuk

Dmytro Shteflyuk — Tue, 22 Dec 2009 14:44:31 +0000

Why not use capistrano multistage?

Comment on Deployment setup automation by Assaf

Assaf — Tue, 17 Nov 2009 08:00:18 +0000

Have a look at Necktie: http://github.com/assaf/necktie/

It came out of a similar approach, but my Capistrano scripts quickly grew unmaintainable. So instead I check my Necktie script into Git, and use a Capistrano task (cap necktie) to pull it and run it on the remote server. A single script that runs locally (on the remote machine) is easier to work with.

http://blog.labnotes.org/2009/11/04/necktie-dress-to-impress/

Comment on Deployment setup automation by Julian Simpson

Julian Simpson — Tue, 10 Nov 2009 15:15:34 +0000

George,

Nice post. I’m very tempted to enhance this by calling a Puppet manifest (or if you really twisted my arm, Chef recipe) to manage all the dependencies, including crontabs, etc. Not a fan of sudo in Capistrano tasks generally but I’d probably make an exception in this case.

Best

Julian

Comment on Asynchronous session content injection by ActsAsFlinn

ActsAsFlinn — Mon, 17 Aug 2009 13:22:21 +0000

Very nice post. We do this to some extent on http://www.fannation.com/ and http://teamusa.org/. You get much better mileage out of action cache than assembling user specific cached fragments into a response. In some places we pass some user specific info via cookie. I’ve found most Rails developers forget you can use cookies and javascript to deliver user customization in favor of writing server side code. I tend to prefer passing the computation onto the client.

Comment on Asynchronous session content injection by Ennuyer.net » Blog Archive » Rails Reading - August 12, 2009

Ennuyer.net » Blog Archive » Rails Reading - August 12, 2009 — Wed, 12 Aug 2009 14:15:06 +0000

[...] nutrun » Blog Archive » Asynchronous session content injection [...]