new choice for network sites: domain

  • I notice that when setting up a network sites we currently have 2 choices, subdir and subdomain.

    I’d like to see a 3rd choice – domain.

    I have a handful of wp blogs I host for friends/family. These folks all have their own “vanity” domains that I’ve registered for them. I do this on a FreeBSD box that runs apache, with virtual named hosts (so a single IP hosts all of the vanity domains). I have installed 3.0-alpha on the (virtual) site https://wpmaster.my.site .

    I have selected “subdomain” as the network site choice for each of the sites I host, which means when I add ‘foo.com’ as a subdomain site, it gets set up as foo.com.wpmaster.my.site, so I have to go thru and correct the URLs for it in the config. Not a huge deal, but it would be “friendlier” if I didn’t have to do it at all.

    Finally, while the “Upload Path” is already correctly handled, I have to figure out what to do about the “File upload URL”. I figure something could be done about this as well.

Viewing 6 replies - 1 through 6 (of 6 total)

  • I don’t think you have a WordPress issue as much as just a server administration issue. I think (and correct me if I’m wrong) that multiple domain names resolve to a single server ip address using name based virtual hosts every day.

    Just an after thought – I’m not sure I grasp your naming conventions:

    I have installed 3.0-alpha on the (virtual) site https://wpmaster.my.site

    Each name based virtual host would, at the very basic level, be configured something like this (as well as a virtual host configuration for the existing host, plus the ServerAlias directive for each virtual host);

    NameVirtualHost *

    <VirtualHost *>
    ServerName https://www.domainone.com
    DocumentRoot /www/domainone
    </VirtualHost>

    <VirtualHost *>
    ServerName https://www.domaintwo.com
    DocumentRoot /www/domaintwo
    </VirtualHost>

    Thread Starter guygadboir

    (@guygadboir)

    Clayton,

    I could be missing something in how I have things set up.

    How do you think this should work? I don’t see that this has much, if anything, to do with the IP that is used.

    I’m talking about the network site capability of 3.0-alpha. I do not want to install and maintain wordpress in each of N DocumentRoot directories. I’m talking about a single installed instance of WP supporting multiple sites.

    Harlan

    Ahhh… I did not pick up on the fact that you were experimenting with the Multisite feature set in WordPress 3.0 alpha. That’s what I get for staying up so late! Sorry if I created unnecessary confusion. I completely overlooked the 3.0 alpha reference in your first post.

    ??

    I do not want to install and maintain wordpress in each of N DocumentRoot directories.

    You will be installing WP once, preferably at root https://example.com.
    To support multiple sites with that one installation, you will need to create sub-blogs in either via subdomain or subdirectory structure. Either way, these are VIRTUAL subdomain/subdirectory structures. By creating such, you can import content to each sub-blog, then use Domain Mapping plugin to point domain names to respective sub-blogs. That’s the way we’ve beeing doing it with WPMU.

    Thread Starter guygadboir

    (@guygadboir)

    I’ll look at the domain mapping plugin, thanks.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘new choice for network sites: domain’ is closed to new replies.