If you plan to develop dynamic pages using server-side languages such as PHP, set up a testing server to generate and display dynamic content while you work.
The testing server can be your local computer, a development server, a staging server, or a production server.
For a detailed overview about the purposes of a testing server, see David Powers’s article, Setting up a local testing server in Dreamweaver CS5.
Setting up a testing server allows you to test all your dynamic code safely without causing any damage to your live website.
You can also work virtually uninterrupted from network failures and Internet outages that might keep you from uploading everything onto a remote server.
In addition by having a local test server, you do not have to waste any time uploading, testing, fixing, reuploading, and retesting your pages.
So if you are testing layouts, shopping carts, or any other script – set up a testing server.
Another benefit of a testing server is that Dreamweaver automatically syncs dynamic documents to your testing server when you open, create, or save changes made to dynamic documents. For more information, see Automatic pushing of dynamic files.
Analytics and load times will not be accurate unless you are accessing the site from a remote location.
This is especially true of load times – since loading a web site from your local computer is always faster than loading the same web site through a network.
Before you set up a testing server from within Dreamweaver, you must set up and install the following:
- A web-server such as Apache
- A database server such as MySQL
- Server-side language such as PHP
Specify Basic options just like you would for a remote server connection, and then click the Advanced button. While setting up the basic options, make sure you specify a Web URL in the Basic screen.
For information on setting up a remote server connection, see Connect to a publishing server.
For more information on the web URL for the testing server, see About the Web URL for the testing server.
You must specify a Web URL so Dreamweaver can use the services of a testing server to display data and to connect to databases while you work. Dreamweaver uses the design-time connection to provide you with useful information about the database, such as the names of the tables in your database and the names of the columns in your tables.
A Web URL for a testing server consists of the domain name and any of your website’s home directory’s subdirectories or virtual directories.
The terminology used in Microsoft IIS may vary from server to server, but the same concepts apply to most web servers.
The home directory
The folder on the server mapped to your site’s domain name. Suppose the folder you want to use to process dynamic pages is c:\sites\company\, and this folder is your home directory (that is, this folder is mapped to your site’s domain name—for example, www.mystartup.com). In that case, the URL prefix is http://www.mystartup.com/.
If the folder you want to use to process dynamic pages is a subfolder of your home directory, simply add the subfolder to the URL. If your home directory is c:\sites\company\, your site’s domain name is www.mystartup.com, and the folder you want to use to process dynamic pages is c:\sites\company\inventory. Enter the following Web URL:
If the folder you want to use to process dynamic pages is not your home directory or any of its subdirectories, you must create a virtual directory.
A virtual directory
A folder that is not physically contained in the home directory of the server even though it appears to be in the URL. To create a virtual directory, specify an alias for the folder’s path in the URL. Suppose your home directory is c:\sites\company, your processing folder is d:\apps\inventory, and you define an alias for this folder called warehouse. Enter the following Web URL:
Refers to the home directory in your URLs when the client (usually a browser, but in this case Dreamweaver) runs on the same system as your web server. Suppose Dreamweaver is running on the same Windows system as the web server, your home directory is c:\sites\company, and you defined a virtual directory called warehouse to refer to the folder you want to use to process dynamic pages. The following are the Web URLs you would enter for selected web servers:
ColdFusion MX 7
Jakarta Tomcat (Windows)
By default the ColdFusion MX 7 web server runs on port 8500, the Apache web server runs on port 80, and the Jakarta Tomcat web server runs on port 8080.
For Macintosh users running the Apache web server, your personal home directory is Users/MyUserName/Sites, where MyUserName is your Macintosh user name. An alias called ~MyUserName is automatically defined for this folder when you install Mac OS 10.1 or higher. Therefore, your default Web URL in Dreamweaver is as follows:
If the folder you want to use to process dynamic pages is Users:MyUserName:Sites:inventory, then the Web URL is as follows:
For more information, see Choose an application server.
A dynamic document is automatically pushed to the testing server when you edit and save it in Live view or Code view. If you want to disable auto push of dynamic files, you can do so in the server settings. For more information, see Disable auto push of dynamic files.
When the files are auto-pushed, Dreamweaver also pushes the dependent files if they are not present on the testing server. If the dependent files are already present on the server, then only the server-side document is pushed to the testing server.
Scenario 1: You make changes to the source code and dependent files. The focus is in the source code when you click Save.
In this case, the following dialog box that lists all the affected, dependent files appears:
You can then choose the files that you want to push to the testing server.
Note: You can select Always Auto Save the Dependent Files to not see the prompt for subsequent operations. To revert this preference at any point in time, go to the settings of the testing server (Site Setup), and in the Advanced tab, uncheck Always Auto Save Dependent Files.
Scenario 2: You make changes to the source code and dependent files. The focus is on one of the dependent files when you click Save.
In this case, only the dependent file is saved and pushed to the testing server.