djspicerack
Feb 15 2004, 08:14 PM
Is it possible for me to post cross-server to host a blog on a site where I don't have CGI/Perl/SSI access? I have a current MT installation, but have another domain/blog that I'm hosting elsewhere that I'd like to have MT run on. Unfortunately, I don't have the ability at this time to host the software package on that server. Adding a new blog doesn't allow me to do this, because all the paths, et al are for local directories.
Any ideas?
charle97
Feb 15 2004, 08:16 PM
only way is to install mt on the server.
djspicerack
Feb 15 2004, 08:28 PM
figured as much. thanks for the quick answer.
kadyellebee
Feb 15 2004, 08:34 PM
Since its a different server, a regular PHP probably isn't an option, but maybe you could use some sort of a RSS parser to pull your MT blog's feed into the other site. Would that help?
Kristine
djspicerack
Feb 16 2004, 05:03 PM
Kristine,
Definitely a possibility - looking into it to see what I can figure out. I might just have to suck it up and upgrade the hosting, =)
strab
Feb 16 2004, 06:06 PM
actually i've similar problem - i want to run my movable on one host (one server) and to have archives and blog on another one.
the one i want to run MT on is fast and the other one is spacious.
adamg
Feb 17 2004, 12:45 PM
I'm doing this now. No doubt in the most inefficient method possible, but here's what I did:
On the server on which I have MT and MySQL running, I set up a dummy directory for MT to build its entries in. The path to that goes into the local paths in the Weblog config. But in the URL boxes, I put the URLs for the non-MT server.
When I add an entry to the blog, I run a script via my telnet client (Secure CRT, which supports 'em) that in turns runs a .login alias on server 1 that tars and gzips the blog data, then ftps it to server 2, where the telnet script calls another .login alias that unzips and untars the blog data to the appropriate directory (rsync would be a much better way to go, but server 2 doesn't support it).
From the user perspective, what this means is that if he clicks on the Comments box, he gets comments immediately, served up via Server 1. But if he goes to the permalink, he won't see the comments until the above process is run.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.