Textpattern Support Forum

Glad you got it working and thanks for posting the tip. One suggestion… Your tip gives the impression that you need to download Textpattern for every domain you install or upgrade (the “wget/tar” step). This is not the case. You only need to run that step the first time you install (or upgrade to) a given version of Textpattern.

Following the steps in your tip, you are going to end up with an extra (unused) copy of Textpattern in every domain directory.

Sam – another question. I have updated all the sites on Joyent successfully with the exception of my home site.

In that sub-domain I have extra installs for the two templates I created:

/users/home/me/domains/jonathanstubbs.com/web/public/textpattern
/users/home/me/domains/jonathanstubbs.com/web/public/txp-minima/textpattern
/users/home/me/domains/jonathanstubbs.com/web/public/txp-minima-photoblog/textpattern

What’s the best way of handling this?

I made it that way some time ago – the installs are for two TXP templates I made. Links below. Might be a way to put them in sections but I haven’t figured out how to yet ;-)

Last edited by jstubbs (2009-09-15 20:30:52)

That would be a good idea and I’ll work on that. This would be a good use-case for sub-sections!

One more question – in the base install of multi-sites we have /web/textpattern/textpattern – just wondering why the second folder is required or if I missed something.

jstubbs wrote:

Has anyone successfully upgraded from 4.2 to 4.3 in a multi-site setup? Have to do this sometime and any feedback appreciated. Using the Joyent script by Sam.

Yes. I don’t use Sam’s script, and my setup is slightly different from the stock multisite configuration. Here’s a sketch of the file tree I’m using:

shared/
	js/
		editarea_0_8_2/
		jquery.cycle/
txp/
	multisite/
		rpc/
		sites/
			bar.com/
				admin/
				private/
				public/
					.htaccess -> ../../htaccess/.htaccess
					css/
					css.php
					files/
					images/
					index.php
					jquery.js -> ../../../../textpattern/jquery.js
					js/
						jquery.cycle -> ../../../../../../shared/js/jquery.cycle/

foo.com/ htaccess/ .htaccess textpattern -> ../src/textpattern-4.3.0/textpattern/ textpattern-4.2.0 -> ../src/textpattern-4.2.0/textpattern/ textpattern-4.x -> ../src/4.x/textpattern/ plugin_cache/ src/ 4.x/ textpattern-4.2.0/ textpattern-4.3.0/

The main difference being the textpattern item at the top level of the multisite directory. This is a symlink to the actual textpattern directory of the chosen Txp version in the src directory. To upgrade all sites, all I need is to change this symlink. (As you can see, I keep standby symlinks to the various Txp versions ready, so I just need to rename the symlinks to swap versions.)

Other notes:

I use a common .htaccess file for all sites that don’t have special requirements. Again, easier upgrade path.

This is my local setup, so I also have the plugin cache in there. (I really do not recommend using a plugin cache on live sites.)

The shared directory at the very top level contains javascript packages in use on various sites, including non-Txp sites. An example symlink is shown in bar.com/public/js/. Also note the symlink to jquery.js. This is a symlink to another symlink. Yes, this works.

Couple of other notes