[fusion_builder_container hundred_percent = & #8220; no & #8220; equal_height_columns = #8220 NO #8220; menu_anchor = #8220; & #8220; hide_on_mobile = #8220; small-visibility, medium-visibility, large-visibility & #8220; class = & #8220; & #8220; id = & #8220; & #8220; background_color = #8220; & #8220; Background_Image = #8220; & #8220; background_position = & #8220; center center & #8220; background_repeat = #8220; no-repeat & #8220; fade = #8220 NO #8220; background_parallax = #8220; none & #8220; parallax_speed = #8220; 0.3 & #8243; video_mp4 = #8220; & #8220; video_webm = #8220; & #8220; video_ogv = #8220; & #8220; video_url = #8220; & #8220; video_aspect_ratio = #8220; 16: 9 & #8243; video_loop = #8220; yes & #8220; video_mute = #8220; yes & #8220; overlay_color = #8220; & #8220; video_preview_image = #8220; & #8220; border_size = #8220; & #8220; border_color = #8220; & #8220; border_style = #8220; solid & #8220; padding_top = #8220; & #8220; padding_bottom = #8220; & #8220; padding_left = #8220; & #8220; padding_right = & #8220; & #8220;] [fusion_builder_row] [fusion_builder_column type = & #8220; 1_1 & #8243; layout = & #8220; 1_1 & #8243; background_position = & #8220; left top & #8220; background_color = #8220; & #8220; border_size = #8220; & #8220; border_color = #8220; & #8220; border_style = #8220; solid & #8220; border_position = #8220; all & #8220; spacing = #8220; yes & #8220; Background_Image = #8220; & #8220; background_repeat = #8220; no-repeat & #8220; padding_top = #8220; & #8220; padding_right = #8220; & #8220; padding_bottom = #8220; & #8220; padding_left = #8220; & #8220; margin_top = #8220; 0px & #8220; margin_bottom = #8220; 0px & #8220; class = & #8220; & #8220; id = & #8220; & #8220; animation_type = #8220; & #8220; animation_speed = #8220; 0.3 & #8243; animation_direction = #8220; left & #8220; hide_on_mobile = #8220; small-visibility, medium-visibility, large-visibility & #8220; center_content = #8220 NO #8220; last = & #8220 NO #8220; min_height = #8220; & #8220; hover_type = #8220; none & #8220; link = & #8220; & #8220] [fusion_text]
Working with a webhosting or WordPress staging website on Plesk Onyx
If you own a production website and are planning major changes to the website, then you should consider setting up a staging website. This is a separate location on the server where you can import updates to a copy of a web page and test it before using it as a production Web site.
Our recommendation if you only have one domain without a separate development domain: staging.yourdomain.tld
We recommend that you work with a staging site as follows:
- Think about where you want to host the development copy and prepare the development environment. You can host the copy in the same web space, in a separate web space on the same server, or you can upload it to an FTP account on another server.
If you select the same web space, you must first set up a new web page by adding a domain or subdomain.
- (Optional step) If you are setting up your development environment under your account in Plesk and using APS applications through Plesk (in the section applications) for your production website, you must install the desired website applications in your development environment in the same subdirectory as you use for your production website. This step is optional. However, doing so saves you having to manually change database connection settings in the application scripts.
- Make a copy of the web page and place it in the staging environment.
- Make copies of the databases used by the website and deploy them in the staging environment.
- Change the database connection settings in the scripts to point to the databases in the staging environment.
- (Optional step) Finish the setup of the APS applications. Go to the section applications for your development website, look for the application in the list of installed applications, open the window settings and save the parameters again. As a result of this process, the APS scripts should no longer point to the production database and the application should reconnect to the database copy. This step is necessary if APS applications have been installed via Plesk in your production website and you have completed step 2 of this guide.
- Make the necessary changes to the web page copy in the staging environment and test the web page to make sure everything is working as intended.
- Publish the updated website. For this purpose, the document root of the production website must point to the location of the staging website.
To set up a staging webpage for testing purposes:
- Go to Web Sites & Domains.
- Click either Add a domain or Add subdomain.
We recommend that you use a subdomain for staging purposes.
- Follow the instructions below Add domains or Add subdomains in front.
If you do not want your staging site to be available to internet users, you should not register the newly added domain name or subdomain name with a domain name registrar, or one
.htaccessFile (for Linux hosting) to restrict access.
To create a copy of Web page files:
- Go to Web Sites & Domains and find the name of the web page you want to copy.
- click on Copy website.
- To copy the Web page files to the root directory for documents on an existing Web page, follow these steps:
- Select the option Website in Plesk out.
- Select the destination web page in the menu Name of the website out.
- Specify what should happen to the files that already exist in the target directory.
- To copy the Web page files to an FTP account located on this or another server, you must do the following:
- Select the option FTP memory out.
- Specify the host name of the server and the credentials for connecting to the FTP account.
- In the field FTP connection method keep the selection of the option Active mode at. If Plesk can not connect to the external FTP account, select the option here Passive mode out.
- click on OK.
If the Web page uses scripts that reference a database, copy the database to the staging environment:
- If the database is hosted on the same server (managed by Plesk) then copy as described below.
- If the database is hosted on a different (non-Plesk managed) server, use the utility
mysqldumpto export the database. Then move the data dump file to the staging environment and drop it there. Edit the web page scripts in the staging environment so that they connect to the copied database.
To copy a database from Plesk managed server:
- Go to Web Sites & Domains > databases.
- In the database listing, click next to the database you want to copy Copy.
- Specify the following:
- Target database server, You can select the same Plesk managed database server or a database server located elsewhere. For an external database server, specify the host name or IP address and credentials for access: that is, the username and password of a system user who has database authority and can therefore create databases and database tables.
- Target database, You can either create a database or copy the data to an existing database.
- Make a complete copy, Leave this option selected if you want to copy the database structure and all data.
- click on OK.
The database copy is deployed on the destination server.
- Edit the web page scripts in the staging environment so that they connect to the copied database.
Once the web page copy has been updated in the staging environment and is ready to be put online, you can publish it. To do this, follow the steps below.
To publish the updated Web page in the production environment:
- Go to Web Sites & Domains.
- In the list of domain names, search for the address of your production website and click on its link.
- in The Field documents master specify the root of the staging webpage.
- click on OK.
Now, the updated web page copy, which is located in the Staging Web site directory, is available to visitors who access the Internet address of your production Web site.
[/ Fusion_text] [/ fusion_builder_column] [/ fusion_builder_row] [/ fusion_builder_container]