WEBDEV Concepts

212 Part 7: Deploying a Web site Deploying a dynamic site in practice When developing a dynamic site (in Session or AWP), one of the important phases consists of deploying this site on a Web server (at a hosting company or in Intranet) Several deployment methods are available: • deployment to PCSCloud : Paid turnkey solution. For more details, see http://www.pcscloud.net . • remote deployment (via HTTP) on a WEBDEV Application Server or WEBDEV Cluster : recommended method when the server is not directly accessible. Remark: for backward compatibility, it is also possible to perform a remote deployment via FTP. • deployment by package : recommended method when the server is not directly accessible and when its characteristics are unknown. • deployment by physical media : recommended method when the server is easily accessible. • deployment via a Docker image . Remarks : • For each Web server that hosts WEBDEV sites, the hosting company must own a license for the WEBDEV Application Server. • To create the setup of a site, go to the "Project" tab, "Generation" group, expand "Deploy site" and select "Generate and deploy site". To deploy a static site, see Deploying a static site or a PHP site. 1 Generating a library Before performing a setup, all the objects found in your dynamic site (in Session or AWP mode) must be included in a library.. A library is a file that contains all the objects created during development (database description, page description, compiled source code, etc.).. The HTML pages and the images are not included in the library. The library is automatically implemented when creating the setup procedure. Once the library is created, the wizard for setup creation starts. You can choose to perform: • deployment to PC SOFT Cloud : PC SOFT offers a hosting platform based on the Cloud Computing model: you deploy without worrying about hardware constraints and you are billed based on your applications’ real usage. A PC SOFT Cloud account is required to perform this type of setup. The wizard prompts you to create this Cloud account if necessary. • remote deployment (via HTTP or FTP) on a WEBDEV Application Server or WEBDEV Cluster : Before performing a remote setup, the hosting company must have configured the web server (and the WEBDEV Cluster if necessary) and sent the parameters needed to install the site. • a remote deployment package : A deployment package is an executable containing all the elements required to deploy a WEBDEV site. This package can then be executed from any computer to install the website on a remote WEBDEV Application Server or a WEBDEV Cluster (via HTTP or FTP). To create this type of setup, there is no need to know the characteristics of the WEBDEV accounts on the Web server. • a setup by physical media : The wizard allows you to create a setup program for your site. Then, this program will be supplied to the hosting company and it will be used to install your WEBDEV site on the Web server. To install your WEBDEV site, the hosting company must: 1.  Install the WEBDEV Application Server on the Web server (if necessary). 2.  Install your WEBDEV site by running the I nstall. exe executable of your setup. Remark : It is also possible to create a setup as stand-alone physical media, containing the setup of a WEBDEV Application Server limited to 10 connections. This solution is ideal for proof-of- concepts presented on a laptop.