Imprimir

Advanced Deploy

Pre-Requirements:

  • Web Server (ex: Apache, IIS).
  • PHP version 5.6 or later.
  • Access to the project database that’s going to be used in the production environment.

Note: Different from the typical deploy, where the setup of the directories is the done from ScriptCase using the default settings, the advanced deployment allows you to choose the directories is according to the architecture of the server where it’s going to be deployed to.

1 - Access your project and choose the option “Project -> Deploy Applications”, available on the top menu.

ScriptCase "Project ScriptCase “Project” Menu

2 - After clicking the on Deploy, you’ll have the option to deploy all the applications from the project or you can select the applications that you want to deploy.

  • All Applications

Select the applications to be deployed Select the applications to be deployed

  • Select the applications

Select the applications to be deployed Select the applications to be deployed

  • List of available applications

Select the applications to be deployed Select the applications to be deployed

3 - Choose the type of deploy that you’ll use (Advanced).

Select the applications to be deployed Select the applications to be deployed

4 - Create a template for the deployment so that the settings can save and reused each time you deploy the current application.

Choose the name of the template to deploy Choose the name of the template to deploy

5 - Define the structure of the directories of the production environment defined in the production server. You can see two examples of different setup examples.

  • Example 1:

Note: It’s necessary to create the directories in the production server, so that it can store the Production environment (Common Libraries) of the deployment, remembering that the documents directory needs to be informed the absolute path until the folder. On this example, we’re using the production folder.

Example 1: Choose the structure of the deploy folders Example 1: Choose the structure of the deploy folders

Example 1: Choose the structure of the deploy folders Example 1: Choose the structure of the deploy folders

  • Example 2:

Note: On this example, it’s necessary to create the image, documents and temporary directories, on your production server, remembering that the documents directory needs to be informed the absolute path. Relating to the Production Environment (Common Libraries), it’s necessary to take the “prod” folder generated at the end of the deploy to the server. In this case, we’re using different directories form the previous example.

Example 2: Choose the structure of the deploy folders Example 2: Choose the structure of the deploy folders

Example 2: Choose the structure of the deploy folders Example 2: Choose the structure of the deploy folders

Note: On both examples on top, in case you want after the conclusion the deployment process, there’ll be a link to download and deploy the common files, check the option “Deploy with common files (css, buttons, images, messages)”.

  • Common Libraries Folder: Library and service package used by the deployed applications. Inform the relative path to the prod directory, ex: /production/prod or /prod
  • Images Folder (used for uploading service): Folder where will be stored all the images, when an application uses a field of the type “Image (File Name)”. Inform the relative path to the image directory: /production/file/img
  • Temp Folder: Folder where be stored the generated temporary files during runtime of the applications. The files of this directory will be removed periodically according to the specific settings, by default it’s 120 minutes. Inform here the relative path to the tmp directory, ex: /production/tmp or /temporay_files/tmp
  • Documents Folder (used for uploading serviced): older where will be stored all the documents, when an application uses a field of the type “Image(File Name)”. Absolute Path (Full Path) to the doc directory, ex: C:/Apache/htdocs/productions/file/doc or C:/Apache/htdocs/my_documents/doc

Note: The Character “/”, means the root of the Web Server, it’s used for relative paths.

6 - Define the connection name that’ll be used by the project after deploying.

Choose the name of the connection Choose the name of the connection

7 - Choose the the way method of deploy that’s going to be used. ScriptCase offers 4 options:

  • Generate the ZIP with the applications (recommended):
    • The final process that’ll be give you a link to download the deploy package.

Select the ZIP method Select the ZIP method

Note: This option is recommended because it doesn’t on other services to be done.

  • Deploy on a server directory:
    • Deploys the project in the informed directory. This option should be used, in the case that the deploy is going to be in the same sever where ScriptCase is installed, otherwise this option isn’t valid.

Choose the Directory to deploy Choose the Directory to deploy

  • Deploy on a FTP server:
    • Deploys the application automatically on a remote FTP server.

 Select the FTP method Select the FTP method

  • FTP server: Server where you’ll deploy your project. Inform the domain or IP of the server.
  • User: User for the FTP server in the production, remembering that the user need to have permission to write in the server folder, otherwise it won’t work.
  • Password: Password for the FTP user.
  • FTP Folder: Server directory where the project will be deployed in.

Note: To use this option it’s necessary that the server to offer the FTP service the user to have write permission on the server folder.

  • Deploy on a SFTP server:
    • Deploys the application automatically on a remote SFTP server.

Select the SFTP method

  • Select the SFTP method *

  • SFTP server: Server where you’ll deploy your project. Inform the domain or IP of the server.
  • User: User for the SFTP server in the production, remembering that the user need to have permission to write in the server folder, otherwise it won’t work.
  • Password: Password for the SFTP user.
  • SFTP Folder: Server directory where the project will be deployed in.

Note: To use this option it’s necessary that the server to offer the SFTP service the user to have write permission on the server folder.

8 - On the final process you’ll a report with all the application deployed with the download link of the project, also with the common libraries, that are the necessary routine to run the applications on the production environment, that’s why they are required to upload with the deployment.

Last Page of Deploy Last Page of Deploy

Note: The advanced deploy requires that you download the “Production Environment”, that is the package that contains the common libraries. If you don’t want to download the Production Environment (Common Libraries) from the link generated by the deploy, you can download it by Clicking Here. If you deploy the project again, you don’t need to download the common libraries, but this information isn’t valid if the common libraries were updated in a new ScriptCase release.