|
|
|
|
- Overview
- Installing the files of a static site on a Web server
- Compressing and grouping the files of a remote site in archives
- Restoring the files found in an archive
- Notes
Installing the files of a static site on a Web server To install the files of a static site on a Web server: - Start WDDeploy: on the "Tools" tab, in the "Web utilities" group, click "WDDeploy".
- Create or select the profile corresponding to your site. The characteristics are entered in several tabs:
- General information:
- name of the profile.
A default name is automatically given to the profile. This name can be modified. - location of local files of the site ("<MyProject>_WEB" subdirectory for a static WEBDEV site).
- address of WEBDEV site.
- deploy a single language for the site. If this option is selected, your site can be deployed in one of the languages supported by the project. Caution: in this case, your site must not use any options or functions allowing to change the language or to support several languages.
- Connection
- location of files of deployed site (network directory or FTP server).
- characteristics of the FTP server used to update the site (deployment via FTP only).
These characteristics are supplied by the hosting company. Remark: To use an SFTP server, type an address such as "sftp://<Server address>".
- Filters
List of filters applied to the files to install. The filters are applied to the files that must be installed on the Web server. Two options are available:- "Only process the files that correspond to the filters": the files installed on the Web server will be the files affected by the filters.
- "Process all the files except those that correspond to the filters": the files installed on the Web server will be the files not affected by the filters.
- Remote access
Used to define a remote access to use before accessing the FTP site (when the site is accessed by a modem for instance).
- Click the "Prepare" button. WDDeploy prepares the list of files to install.
For an update, WDDeploy compares the files found on the development computer and the files already installed. - Specify (if necessary) the different actions that must be performed during the synchronization on the different files to install:
- "Local copy" button: copies the selected files from the remote site to the local site.
- "Remote copy" button: copies the selected files from the local site to the remote site.
- "Remote deletion" button: deletes the selected files from the remote site.
- "No action" button: performs no operation on the selected files.
- Click the "Synchronize" button. The site files are automatically copied to the location specified in the profile.
Remarks: - The "Options" button is used to specify the synchronization options. For more details, see Remarks.
- When creating a new profile, a wizard helps you enter the parameters and offer preset profiles fro the main hosts.
Compressing and grouping the files of a remote site in archives To compress and group the files of a remote site in archives: - Start WDDeploy: on the "Tools" tab, in the "Web utilities" group, click "WDDeploy".
- Click on "Save".
- Enter the name of the archive to create (".WDZ" file) and specify the creation directory. The files found in the remote site specified in the profile are automatically compressed and grouped in the created archive.
Restoring the files found in an archive To restore the files found in an archive: - Start WDDeploy: on the "Tools" tab, in the "Web utilities" group, click "WDDeploy".
- Click the "Restore" button.
- Select the archive file (".WDV" file) to restore.
- Select the directory in which the files found in the archive must be restored and validate.
The options of WDDeploy are as follows: - "Display the tooltip on the table of files": displays a tooltip that describes for each hovered file:
- the name of the file as well as the date and time of file creation on the development computer.
- the name of the file as well as the date and time of file creation on the deployment computer.
- "Don't process the subdirectories": does not take into account the sub-directories of the local site when the site files are deployed.
- "Don't propose to modify the local site, even if the remote files are more recent": does not update the remote files more recent on the development computer. When preparing for synchronization, WDDeploy will not propose to replace the local files by the remote files (even if the remote files are more recent).
- "Don't display that files that are already synchronized": displays the files modified since the last synchronization only.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|