Trying to simplify/understand multi-site

  • Resolved sdoss

    (@sdoss)


    13 years, 9 months ago

    I’m hoping to get some confirmation here that I am understanding what I’m reading re multi-site installation, and how/why it works, as well as ending with a couple of questions I’m still unclear on.

    Multi-site allows you to create/host more than one site in a single instance of WordPress. That’s easy.

    Multi-site can make use of ‘sub-domains’ or ‘sub-directories’. Also easy.

    If using a ‘sub-domain’ method:
    WordPress MUST be installed in the document-root directory, and Apache configured with a domain name pointing to WordPress
    Sites created in WordPress must also be mapped in WordPress to the desired domain (via a WordPress plug-in)
    DNS record of the desired domain points to the host server; Apache on the host server is configured to point to the WordPress domain, and WordPress, on recognizing the original domain request, points to the appropriate site.

    Am I right so far?

    If using a ‘sub-directory’ method:
    WordPress COULD be installed in a sub-directory of document-root, and Apache configured to point to this sub-directory
    Sites created in WordPress do NOT need mapping
    DNS record of desired domain points to the host server; Apache on the host server is configured to point to WordPress domain/site

    Now the question is, am I anywhere close??

    I’ve installed WordPress in a sub-directory of document-root, and activated the multi-site option as per the instructions posted here. (installed on a debian server, with apache and php 5.2.5) Because WordPress is in a sub-directory, my only option was to use sub-directories for my sites. My desire is to use WordPress to develop and serve the web pages without an obvious ‘redirection’ in the url. If someone goes to https://www.site1.com, I’d like the url to consistently read https://www.site1.com/page…

    So here’s the real question: If I want site 1 to be accessed via https://www.site1.com, and site 2 to be accessed via https://www.site2.com, and not have the url display a redirect, do I use sub-domain? Or can I use sub-directory? And if I can use either, can you point me to the documentation that tells me that? And how? And why?

    Apologies if the above sounds ignorant, but my eyeballs are bleeding after spending a week of searching/reading all I can find on multi-sites ??

Viewing 2 replies - 46 through 47 (of 47 total)
  • Thread Starter sdoss

    (@sdoss)

    Possibly another note of interest: I turned on debug in the main Apache error log, and now, in addition to the mod_python notice above, I’m seeing the following [debug] message:

    [debug] prefork.c(1016): AcceptMutex: sysvsem (default: sysvsem)

    prefork module in main configuration:

    <IfModule mpm_prefork_module> /etc/apache2/apache2.conf (101)
    StartServers 5 /etc/apache2/apache2.conf (102)
    MinSpareServers 5 /etc/apache2/apache2.conf (103)
    MaxSpareServers 10 /etc/apache2/apache2.conf (104)
    MaxClients 150 /etc/apache2/apache2.conf (105)
    MaxRequestsPerChild 0 /etc/apache2/apache2.conf (106)
    </IfModule>

    Still seeing NO messages in the WordPress vs log.

    Just throwing things out there hoping someone will be able to help.

    Thread Starter sdoss

    (@sdoss)

    After a couple of weeks of monitoring multiple things – system resources, various logs in various stages of debug modes, load times for my WordPress pages vs non-WordPress pages in an attempt to determine what was causing my WordPress pages to be excruciatingly slow in loading, I hit upon an Apache directive that seems to have been a big part of the problem.

    The directive is a part of mod_access. Allow, Deny, and Order seem to work together to determine which hosts can (or cannot) have access to the directory for which you’ve set the directives. I don’t know what the default settings are, but I noticed in the virtual host for my WordPress domain, it was set to Allow from all. This may have been turned on in conjunction with the AllowOverride all (but I’m unsure at this point).

    Anyway, I changed that setting to do neither allow nor deny – and viola! Load times immediately went down to anywhere from 2.1 to 42 seconds, as opposed to the 1.5 to 4 minutes (MINUTES!!) I’d been seeing.

    Of course, 42 seconds is still way too long for a page to load, but, at least now I can look more closely at the components of my page, instead of tearing my hair out trying to figure out where the hamster was falling off the wheel!

    Also, in this process, I’ve found FireBug for Firefox to be an extremely informative tool, in conjunction with YSlow (although YSlow is more general in it’s info).

    So, until I find other things that may be causing the speed issues in my site, we’ll call this one resolved. Thanks for all your help.

Viewing 2 replies - 46 through 47 (of 47 total)
  • The topic ‘Trying to simplify/understand multi-site’ is closed to new replies.