Hello everyone,

Is there any documents on how to make an installation of Movable Type on multiple servers ? On this document - http://www.movabletype.org/documentation/e...chitecture.html there are many different configuration possible, but how to implement them ? I like to have a system where comments are processed on a separate server and where the page server is also separate for load balancing.

Are multiple installations of the software necessary ? Is there changes to the mt-config.cgi file ? Is this the use of the RebuildQueue, or are the changes in the templates to point to comment cgi on different server ?

Thank you all kindly for your patience and your help.

Sanj

I'd like to know the same thing -- I'd like to set up three servers: one for the editors, one for comments, and one just to push static files out over the wire. And I'm looking for the nuts and bolts of how to do that.

This forum post is coming up in the google results for "movable type multiple servers", so I thought I'd ask here, in hopes that I can lure the answer out of the underbrush! :)

Any help would be greatly appreciated.

If you look at the enterprise documentation http://www.movabletype.org/documentation/enterprise/ you should find some useful docs.

OtherNiceMan, thanks for replying. About the enterprise documentation, and there being helpful stuff there:
Yeah, that's what I had hoped for, but what I've found there is limited to:
1) The "purty diagrams" page showing some sample architectures but no links to "okay, how would I go about doing this" documentation,
2) Pointers to documentation about the publish queue. Which makes sense and seems promising, but I have questions about how (for instance) you twiddle the bits so that all calls to mt-feedback.cgi and mt-search.cgi go to the FEEDBACK box, and not to the admin box.

The enterprise documentation promising, as far as it goes, but I frankly feel like I'm being shown a bag of rock salt, a bucket of ice, and a cow, and told that I now have everything I need to make a delicious 12-scoop sundae. I'm happy to do the work, but I'd love to be reassured that I'm not the only one who has tried it. Is there a reference implementation out there? Any documentation (just for instance) about how the "adminurl" directive, which I suspect is a key part of things, gets used?

Well, there's the configuration directive documentation: http://www.movabletype.org/documentation/a...fig-directives/

Part of the strategy that I can explain here is that you can use the publish queue to offload certain tasks from one server to another. Jobs for it exist in the database, and so one installation of Movable Type can post a job that another installation of Movable Type will pick up and execute. It's just a matter of setting up a cron job on the second one that runs through the list of tasks to execute.

I can tell you from personal experience with the publisher queue that if you use it aggressively, you can really cut down on the amount of time it takes to post a comment. What I do is have everything but my main index and entry archives set to be published that way.

For more detailed information, you may have to contact 6A or start asking around on the MTOS mailing lists since this is, admittedly, an area where the documentation is not as detailed as it should be.

MikeT, cool: that's reassuring to hear -- partly, I wanted to make sure that there wasn't a neatly-packaged set of documentation out there that I was just overlooking.

I'll carefully re-read the configuration directivo documentation, read up on the publishing queue, and get cozy with The Schwartz. Mostly, I now have a bunch of tactical questions, like whether to use replicated MySQL databases, or have a database that all the boxen connect to.