Textpattern CMS support forum
You are not logged in. Register | Login | Help
- Topics: Active | Unanswered
Pages: 1
Multi-Site Installations
Can someone point towards a painfully detailed step-by-step set of instructions for converting an existing single-site textpattern installation over to multi-site? There is a set of instructions that come along with textpattern as a text file, but I find them boggling. Thanks!
Offline
Re: Multi-Site Installations
Yeah, I’d actually love to run most of my sites off one codebase If it was a more straightforward process.
Offline
Re: Multi-Site Installations
skewray wrote #279101:
Can someone point towards a painfully detailed step-by-step set of instructions for converting an existing single-site textpattern installation over to multi-site? There is a set of instructions that come along with textpattern as a text file, but I find them boggling. Thanks!
There is this tutorial over at TXP Tips but that was written for a Joyent/TextDrive setup and your mileage might vary. As Dale says, its not a straightforward process.
Offline
Re: Multi-Site Installations
I really don’t mind myself how complex the procedure is for converting to multi-site. I just want sensible instructions. For example, the README.txt file starts out with:
There are two slightly different sets of instructions, depending upon whether you prefer to: A. Create separate subdomains for your Textpattern admin areas (recommended), or B. Allow access to the admin area through a subdirectory of your site (the traditional setup).So this leads me to a large number of questions: What is an admin area? My current installation has none. What is in it, and what does it do? Why do I want one? Do I need one for multi-site, or is it optional? Why is A recommended over B? What are the practical considerations that would help me make a choice?
Last edited by skewray (2014-02-20 15:42:33)
Offline
Re: Multi-Site Installations
Every Textpattern install has an admin area. Sometimes it is called the backside vs. the front side. It is where you log in, write articles, administer users, manage sections, pages, forms, etc. In other words, administers the CMS functions of Textpattern. This as opposed to the published website powered by Textpattern.
The choice they are referring to is this:
TextpatternAdmin.YourWebsite.com vs. www.YourWebsite.com/textpattern
The first sets up the admin to be accessed at a subdomain. The latter as a directory within the main domain.
If I recall correctly, part of the reason for using the subdomain option was increased security.
Offline
Re: Multi-Site Installations
skewray
Here’s a link where we started collecting Multi-site install wisdom. fwiw.
Also, fwiw,
I played around with multisites when they first came out, but time-wise it was really easier to go with stand alone sites most of the time rather than hassle with plugins that didn’t work well w/ multi-sites (in particular when the admin was a subdomain), with potential security issues, or with the added complexity of the directory structure.
Last edited by maverick (2014-02-21 03:46:04)
Offline
Re: Multi-Site Installations
Like maverick, I also found multi-sites in its present incarnation to be difficult to update, and there were some criticisms over on this thread which is worth reading.
Offline
Re: Multi-Site Installations
It sounds to me like I was asking the wrong questions. I should have started out asking if multi-site was worth doing at all. I will have to study up on that first, using the helpful liks provided. Thanks!
Offline
Re: Multi-Site Installations
Multi site is really just an afterthought in the land of TXP. I think it should either be a solid feature or jettisoned from core as it confuses people at present.
Drupal has a solid multi-site mechanism, but the downside is… it’s drupal.
Offline
Pages: 1