skip to Main Content

How To Deploy Your DesktopServer Site to a Live Host In a Subdirectory.

The method we recommend for setting up a live hosting environment is to either use a top level domain such as .com, .org, .gov etc, or to use a subdomain where you would use a differentiating word prior to the top level domain (, However, there may be a time that you find yourself in need of deploying your locally developed site to a subdirectory instead. A subdirectory installation is when you have created an installation in a directory beneath your top level domain ( While DesktopServer’s direct deploy method can work in these instances, it requires that the live site directory structure is identical to that of your local environment and that WordPress is installed in the Top Level Domain. Sometimes, this is not the case. In the video tutorial and instructions, we show you how to take a locally developed WordPress website created with DesktopServer and deploy it to a subdirectory on your live domain.

For those of you that would like step by step directions, we have included those as well:

  1. Create WordPress 1-click install
  2. Install to subdirectory of choice
  3. Note database name
  4. Verify that Database Table Prefix matches local prefix table
  5. Verify installation
  6. Delete wp-content directory and all its contents in newly created WordPress subdirectory
  7. Start DesktopServer
  8. Export your local site to an archive
  9. In Export As field, enter top level domain name or subdomain only. Do not enter subdirectory
  10. Select Customize Scrubbing Options (!important)
  11. Change “Replace With” field to have /subdirectory name in the scrubbing options
  12. Open archive
  13. copy database.sql to a file location of your choice (note location in which you stored the file)
  14. FTP local wp-content file to live WordPress subdirectory
  15. On Host, click on phpMyAdmin
  16. Select the database of the new WordPress installation.
  17. Delete all tables in database
  18. Import locally stored database.sql that was extracted from newly created archive
  19. Check to be sure site works
  20. Re-save permalinks