Feedback Print

Typical Deploy

Pre-Requirements:

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

This type of deployment is for users that want the Production Environment (Common Libraries) with the default settings from ScriptCase, the basic setup is done already be ScriptCase.

Follow the process will be described below to realize the Typical Deploy:

Project Deployment

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

ScriptCase "Project" Menu ScriptCase “Project” Menu

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

All Applications

When select this option, all the applications of the project will be deployed.

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

Select the applications

This option allow us to select the applications that will be deployed.

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

List of available applications

Select the applications that you wish to deploy.

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

3 - Choose the type of deploy that you will use (Typical).

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

4 - Choose the initial application.

In this step we also defines if we will send the common libraries with our project.

Select the initial application for the deployment Select the initial application for the deployment

It is necessary to select the common libraries, which are the files responsible for the “Production Environment”. It is necessary to select the common files, for the images, css and custom messages to be sent at the moment of the deploy.

  • Common Libraries(Prod) Contains the used libraries by our applications(CEP, GoJS, etc) and also the informations of connections used by the project.
  • Deploy with common files: This option is obligatory for a project deployment, for the images, css and customized messages be send in the moment of deploy generation.
  • Initial Application: Defines the system initial application.

Generated Files

5 - Generating the files to deploy:

In this step we must select the way that we wish the applications will be generated.

Generate ZIP or Tar.Gz with applications (Option used in this example):

The Scriptcase will generate a file Zip or Tar.Gz. In the end of this process, will be displayed a report of the deployed applications with the download link for download the project.

The file ZIP or Tar.Gz generated, must be decompressed only in the deployment server, to avoid that the files be corrupted.

Select the ZIP method Select the ZIP method

Deploy on a server directory:

Deploys the project in the informed directory. We must inform the absolute path to the deployment 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 is not valid.

Choose the Directory to deploy Choose the Directory to deploy

Deploy on FTP server:

This option generates the files directly in the FTP remote server.

Select the FTP method Select the FTP method

  • FTP server: Server where you will deploy your project. Inform the domain or the server’s IP.
  • 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 will not work.
  • Password: Password for the FTP user.
  • FTP Folder: Server directory where the project will be deployed in.

To use this option is necessary that you have a server that provides the FTP access and an user with write permissions.

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 will deploy your project. Inform the domain or IP the server’s IP.
  • 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 will not work.
  • Password: Password for the SFTP user.
  • SFTP Folder: Server directory where the project will be deployed in.

Note: To use the SFTP option is necessary that the user have permission to write on the server folder.

6 - At the end of the process you will receive a report with all the applications deployed and a download link of the project ready to be published.

The file ZIP or Tar.Gz generated, must be decompressed only in the deployment server, to avoid that the files be corrupted.

Tela final da publicação Last Page of Deploy

Server Directories

7 - In the server root was created a folder(typical) where we will decompress the deployment files.

Server Directories

8 - In the end of the compression process, we must access your project through the browser.

In the first access we must configure the connections in Production Environment.

First Access