4

I'm looking for resources that will help me design an optimum multi-user multi-server LAMP environment.

We currently have 7 servers (2 load-balanced webservers, 2 redundant clustered web-content servers, 2 redundant clustered MySQL servers, 1 VirtualMin Developer server), but am having difficulty determining if what I have done is common/optimum/good practice, etc.

Can anyone point me to any good/great resources for designing (and running) multi-server LAMP environments?

Note: I asked this question on StackOverflow some time ago, but didn't get any great results. Perhaps I should have waited until the end of the Beta (for more of a non-SO audience)

1
  • 1
    you can't spell best practices May 19, 2009 at 15:19

2 Answers 2

2

For configuration management take a look at tools like puppet and chef. There are others you might want to check as well, like capistrano. Also, you want to keep an eye on those servers when they enter production mode. For monitoring, you might want to check Nagios. And there are lots of others, some of them based on rrdtool.

1
  • Thanks, we use nagios very extensively, and are very happy with that. As for puppet and capistrano, our servers are all in clusters, and so there is no manual duplication of data. Haven't heard off "chef" though, I will check that out.
    – Brent
    May 19, 2009 at 15:55
1

Any environment of sufficient complexity (that is, any at all, really) should be under configuration management, whether it be Chef or Puppet. My preference is Chef and there's a set of cookbooks (configuration modules) that will help in setting up end-to-end the entirety of a LAMP stack (or my preference, LAMRails). There's also EC2 AMIs available for setting up an entire Rails infrastructure on Amazon EC2, and this can be a good baseline to look at for considerations about setting up your own environment.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .