Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
[wiki] Multi-site Documentation
I’ve not had to think much about the “sites” folder since it’s inclusion in the core and the multi-site capabilities it provides, but that might be relevant to me soon and I’m not really finding any documentation about it. Certainly not in the wiki, anyway.
It seems to me one good place to link that from would be this section where it talks about the install tree, and specifically in context with the “sites” folder. I’ve added a link, in fact, in the sites folder description in case someone with more knowledge on it than myself would be willing to throw down some notes as a start.
I also think I read somewhere once that a web host can make a difference about how multi-sites are handled, but I’m not positive. If that were true, that would be useful information for people too.
Offline
Re: [wiki] Multi-site Documentation
As a possible model for exploring an example by which to provide instruction (one of other possible examples, naturally), let’s say conference organizers maintained a website powered by a single install but wanted to build/maintain each year’s conference as a mini-site in a subfolder as follows:
mothersite.tld
** 2009.mothersite.tld
** 2010.mothersite.tld
** 2011.mothersite.tld
** etc.
Is that relevant to what the sites folder is about? Each minisite can have it’s own graphic chart?
Offline
Re: [wiki] Multi-site Documentation
Re web host and multisite, a multisite install depends on symbolic links. Not all web hosting accounts allow this.
Re your proposed example, perhaps you are thinking of sites that would share some content/design elements? At any rate, that isn’t what Txp multisite is for. Multisite gets you two main things: a single set of core files to maintain, and the ability to put the admin side into its own domain or subdomain. Each site is completely separate, though, when it comes to content, templates, etc.
Somewhat tangentially, I posted some notes on getting multisite going.
Code is topiary
Offline
Re: [wiki] Multi-site Documentation
I don’t mean for my example to direct conversation in this thread, so if that’s not a good example, please, anyone, give a different one.
jsoo wrote:
…perhaps you are thinking of sites that would share some content/design elements?
Yes and no.
No in that each of the implied annual conference in the example above are unique sites having unique content and unique presentations. The result of different conference committees from year to year. Once a given year passes, the site becomes an archive site in a way (e.g., 2010.mothersite.tld).
Yes in that there would be other Txp sections of the main mother site that would be maintained annually as part of the main site, but separate from the individual conference sites. I didn’t indicate these persistent sections, but they would exist.
The common denominator is that there would always be the same site administrator (the domain owner), but the annual conference sites would effectively be different websites from year to year by different people (except the admin, whose always on hand).
Maybe the sites directory in Txp is not the idea way of handling such a structure. I’ll look at your notes closer and see what clicks. Thanks for writing those up, Jsoo.
Offline
Re: [wiki] Multi-site Documentation
Destry wrote:
Maybe the sites directory in Txp is not the idea way of handling such a structure. I’ll look at your notes closer and see what clicks. Thanks for writing those up, Jsoo.
Should be fine for it, if I’m understanding your example correctly.
Code is topiary
Offline
Pages: 1