Create a staging sub-domain that uses a seperate WP install

  • My main domain ‘www.mydomain.co.uk’ has WordPress multisite installed and is live with lots of content.

    I have recently created a sub-domain ‘stage.mydomain.co.uk’ and can access this sub-domain which displayed a plain WordPress site with no content.

    Im not sure if multisite is the correct way to create this staging environment because I want to be able to have 2 separate databases and code bases. So I can use GIT to roll out to the staging URL for testing, then roll to the live URL afterwards.

    This is my file structure:
    /public_html/ (main WordPress install)
    —/stage/ (another install with staging settings)

    I notice with multisite that you need to point new sub-domains to the main root i.e /public_html/. So how can I point this to /public_html/stage/ instead?

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

  • Did this ever get answered? I am trying to do the same thing and in the multisite setup tutorial it suggests that you set up the subdomain directory as /public_html/

    If so when I copy these files to move them over to a different domain/host won’t it copy all of my multisite files?

    In both these situations I suggest that you run the second website as an independent WordPress installation. Use your web hosting management “sub-domain” feature to map the URL with your prefix to an new directory that IN NOT under /public_html and then install WordPress there with its own database etc.

    You could use GIT for managing your WordPress files, especially plugins and themes, but be aware that MOST of your WordPress website content is in your database and don’t fit well into the GIT model.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘Create a staging sub-domain that uses a seperate WP install’ is closed to new replies.