Typical Deploy
Pre-Requirements
NOTE: Verify here the functions that need to be enabled in your PHP for the good functioning from Scriptcase generated applications.
Verify below the requirements for the generated applications by Scriptcase. To guarantee that applications can run in Production Environment.
1 - Web Server to deployment (ex: Apache, IIS).
2 - Correct PHP Version for applications developed in Scriptcase.
Projects developed in Scriptcase with PHP 7.0 or 7.3 are approved to be published in the following versions of PHP:
- PHP 7.0
- PHP 7.1
- PHP 7.2
- PHP 7.3
- PHP 7.4
Projects developed in Scriptcase with PHP 8.1 are approved to be published in the following versions of PHP:
- PHP 7.0
- PHP 7.1
- PHP 7.2
- PHP 7.3
- PHP 7.4
- PHP 8.0
- PHP 8.1
3 - 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. We will show the entire process of deployment in this documentation.
Project Deployment
Access your project and choose the option “Project -> Deploy Project”, available on the top menu.
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.
Select All Applications
When select this option, all the applications of the project will be deployed.
Select the applications individually
This option allow us to select the applications that will be deployed.
List of available applications
During this process, the Scriptcase list all the Applications in the project so you can select the applications that you wish to deploy.
| Per type | Selecting this option, you can see the list of applications grouped by your respective type. |
| Per folder | Selecting this option, you can see the list of applications grouped by your respective folder. |
Choose the type of deploy that you will use (Typical).
Next, we need to choose the type of desired deployment.
Setting the Typical Deployment
We must define which application will be the deployment initial application. In this step, we also define if we will send the common libraries with our project.
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.
| Deploy with the Common Libraries(Prod) | Contains the used libraries by our applications and also the informations of connections used by the project. |
| Deploy with the 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. |
| Publish with FusionChart Maps | Checking this option, the referred files to the FusionCharts library will be added in the deployment file. |
| Publishing server operating system | This option is obligatory for a project deployment, when you select the operating system, the Scriptcase will create the correct structure for your deployment. |
| Choose the Initial Application | Defines the system initial application. |
Generated Files
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
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.
NOTE: The file ZIP or Tar.Gz generated, must be decompressed only in the deployment server, to avoid that the files be corrupted.
Deploy on a server directory
Deploys the project in the informed directory. We must inform the absolute path to the deployment directory.
NOTE: 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.
Deploy on FTP server
This option generates the files directly in the FTP remote server.
| 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. |
NOTE: 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.
| SFTP server | Server where you will deploy your project. Inform the domain or 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.
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.
NOTE: The file ZIP or Tar.Gz generated, must be decompressed only in the deployment server, to avoid that the files be corrupted.
Server Directories
In the server root was created a folder(typical) where we will decompress the deployment files.
In the end of the compression process, we must access your project through the browser.
NOTE: In the first access we must configure the connections in Production Environment.
