RE: Deploying to multiple production servers

2009-03-17 Thread Justin Scott
Beware the amount of (network) I/O this may generate. You mean like your sig? ;) I think you win the award for lowest message to signature ratio I've ever seen. I realize it may be an imposed thing by your company, but, wow! -Justin

Re: Deploying to multiple production servers

2009-03-17 Thread Tom Chiverton
On Thursday 12 Mar 2009, Philip Kaplan wrote: the process check every couple of minutes, right? That way if there's an Beware the amount of (network) I/O this may generate. -- Tom Chiverton Helping to professionally establish 24/7 B2C principle-centered CEOs as part of the IT team of the

Re: Deploying to multiple production servers

2009-03-17 Thread Tom Chiverton
On Tuesday 17 Mar 2009, Justin Scott wrote: You mean like your sig? ;) I think you win the award for lowest message to signature ratio I've ever seen. I realize it may be an imposed thing by your company, but, wow! Oh, I know, and it is imposed. Soon (soon !) they might let SSH out from

Re: Deploying to multiple production servers

2009-03-12 Thread Barney Boisvert
I've always used rsync to deploy stuff. It's fast and easy, and since it's all command-line driven it's easy to integrate with pretty much any automation framework you might have. Just a matter of looping over your server list and rsyncing to each one. cheers, barneyb On Thu, Mar 12, 2009 at

Re: Deploying to multiple production servers

2009-03-12 Thread Justin Scott
Philip Kaplan wrote: What's the best way to deploy your code from dev to production (without doing 100 manual FTP's...) Scheduled process on each server to check with a master for updated files via robocopy, rsync (there are versions for Windows available), or similar file copy/mirroring

Re: Deploying to multiple production servers

2009-03-12 Thread Justin Scott
Barney Boisvert wrote: I've always used rsync to deploy stuff. It's fast and easy, and since it's all command-line driven it's easy to integrate with pretty much any automation framework you might have. Just a matter of looping over your server list and rsyncing to each one. I would do it

Re: Deploying to multiple production servers

2009-03-12 Thread Jochem van Dieten
On Thu, Mar 12, 2009 at 8:45 PM, Philip Kaplan wrote: Let's say you have a CF application that needs to run on 100 identical Windows servers. What's the best way to deploy your code from dev to production (without doing 100 manual FTP's...) Merge your code onto the image that gets spooled

Re: Deploying to multiple production servers

2009-03-12 Thread Shannon Peevey
These are all good ideas. just a reminder to cksum the code after it is installed to verify that the right code was installed on all machines. On Thu, Mar 12, 2009 at 2:45 PM, Philip Kaplan pkap...@gmail.com wrote: Let's say you have a CF application that needs to run on 100 identical

Re: Deploying to multiple production servers

2009-03-12 Thread Adrian Moreno
Justin already mentioned Distributed File System (DFS). This what my company uses. http://www.microsoft.com/windowsserver2003/technologies/storage/dfs/default.mspx Basically you setup a single server as the Master. It knows where your other servers are. You push files to the Master and it

Re: Deploying to multiple production servers

2009-03-12 Thread Philip Kaplan
I love this list. Rsync, Robocopy and DFS all look like awesome solutions. I like Justin's idea of setting a scheduled process for the webservers to check the master and automatically grab the latest version. I should have the process check every couple of minutes, right? That way if there's an

Re: Deploying to multiple production servers

2009-03-12 Thread Justin Scott
Philip Kaplan wrote: I love this list. Rsync, Robocopy and DFS all look like awesome solutions. I like Justin's idea of setting a scheduled process for the webservers to check the master and automatically grab the latest version. I should have the process check every couple of minutes,