Difference between revisions of "Talk:Server Architecture"

From SoylentNews
Jump to: navigation, search
m (Potential DNS Providers)
Line 14: Line 14:
 
== Automated deployment ==
 
== Automated deployment ==
 
Whatever provider is used, I recommend starting with an automated deployment from the beginning. It's a lot easier than incorporating it later and you'll thank me when you grow. Puppet is easier to work with unless you are already familiar with Chef. --[[User:Dean1012|Dean1012]] ([[User talk:Dean1012|talk]]) 20:17, 20 February 2014 (MST)
 
Whatever provider is used, I recommend starting with an automated deployment from the beginning. It's a lot easier than incorporating it later and you'll thank me when you grow. Puppet is easier to work with unless you are already familiar with Chef. --[[User:Dean1012|Dean1012]] ([[User talk:Dean1012|talk]]) 20:17, 20 February 2014 (MST)
 +
:I don't disagree.  New infrastructure will be rolled out with tools, not by hand.  That's part of the reason why the Management servers are in there.  I'm a big fan of Puppet and Ansible myself [[User:Zford|Zford]] ([[User talk:Zford|talk]]) 21:31, 20 February 2014 (MST)

Revision as of 04:31, 21 February 2014

Potential DNS Providers


Re: DNS providers

I don't know if this is the right place to add this, but i can host secondary DNS (or primary as well if necessary)

sidd

Automated deployment

Whatever provider is used, I recommend starting with an automated deployment from the beginning. It's a lot easier than incorporating it later and you'll thank me when you grow. Puppet is easier to work with unless you are already familiar with Chef. --Dean1012 (talk) 20:17, 20 February 2014 (MST)

I don't disagree. New infrastructure will be rolled out with tools, not by hand. That's part of the reason why the Management servers are in there. I'm a big fan of Puppet and Ansible myself Zford (talk) 21:31, 20 February 2014 (MST)