How to perform a deployment in Scriptcase - Typical

How to perform a deployment in Scriptcase - Typical

Check out the step-by-step of a typical publication of your projects.

Environment prerequisites

Web server configured and compatible with PHP versions approved for Scriptcase applications such as: Apache, IIS or nginx
Extension of the database used in the project connection enables connection creation.
PHP approved for use in the tool's applications. Applications are compatible with environments with PHP version 7.0 or higher. Check the complete list


Projects developed in Scriptcase installations with PHP 7.0 or PHP 7.3 are approved for the following PHP versions

  • PHP 7.0
  • PHP 7.1
  • PHP 7.2
  • PHP 7.3
  • PHP 7.4
    Projects developed in Scriptcase installations with PHP 8.1 are approved for the following PHP versions
  • PHP 7.0
  • PHP 7.1
  • PHP 7.2
  • PHP 7.3
  • PHP 7.4
  • PHP 8.0
  • PHP 8.1

Starting deployment

1. Access the "Project -> Deploy" menu, available on the top menu.




It is possible to start the deployment outside the project, through the drop-down menu:


2. Select the project applications that will be deployed.

If you choose to select applications, a screen will be displayed showing all of the project's applications, allowing you to define which applications will be deployed.

 


3. Select the type of deployment to be carried out, in this article we continue with the Typical option.
In case you need more information about advanced deploy, check out our documentation about advanced deploy, or go to How to perform advanced deploy.



4. Next, the files that will be sent to your server must be defined.


If this is your first publication, check the options: Publish with production environment and Publish with common files.
When selecting the Publish with production environment option, two new options will be displayed
  1. Publish with FusionChart maps - This option defines if the files referring to the FusionChats Maps library (maps.js) will be sent in the deployment. It must be checked if your project uses any map resource.
  2. Operating Systems - This option is mandatory and defines the sending of wkhtmltopdf and phantomjs files based on your operating system, thus reducing the size of the generated file. Select the operating system where your project will be deployed.
See more details about the available options in Typical deploy documentation.

After selecting the options, click on "Next"

 



5. In the final stage of deployment, it is necessary to define the format in which the deployment will be carried out. Choose the desired format for your deployment and click on "Next".


Generating the ZIP with the applications (recommended): At the end of the process will be provided a link to download the deployment package.


Note: This option is recommended as it is the least dependent on other services to be performed.

Deployment on a server directory: Deploy the applications in the directory  informed. This option should only be used if the deployment is made in the same server where the ScriptCase is installed, otherwise the option will not be valid.




If Scriptcase can't find a folder named "teste", an alert screen will be displayed asking for this folder to be created.

Deploy on FTP server: Automatically deploy the applications on a remote FTP server.




Note: To use this option it is necessary to have a server that has FTP access and a user with write permissions in the same folder.


Select the option you would like to deploy and click on "Next". For this example we will use the option "Deploy on a server directory".


6. At the end of the process, a report of the deployment applications will be displayed along with download links, both for the project and for the common libraries, which are the necessary routines for running the applications in a production environment, which is why it is mandatory that they be taken together to the deployment package.



It is important to wait for the deployment process to end and download the file through the interface, to ensure that all applications and libraries were correctly generated and included in the file.

Creating the connection

In the next step, we will create the connection.

Step 1:  
Access your app through the browser at the following address eg: 127.0.0.8092/folder/app_name. You will see a screen like the image below informing that no connection was found. Please click on "Create connection" button to be redirected to the production environment.




Step 2:   The first time you enter the production environment, the password is "scriptcase".



 


On the next screen you will have to set a new password to enter the "production environment".


 Step 3On the next screen you will have to define a new password to enter the "production environment".



 

Step 4: Upon entering the production environment, you will see your connections, click on them and continue the configuration process.




 

Step 5: In this step we choose the DBMS, the database we use in the application.


Step 6: We will inform the Database Server, in ours as the database is on the same machine as the applications, we can call it through ' localhost ', if the database is on another server it can be called through the machine name or IP number, we will inform also the Login and Password to access the database (if any).


Note: For the example, the MySQL database was used.



Step 7: The last step will be to access the application through the browser.




    • Related Articles

    • How to perform a deployment on Scriptcase - Advanced

      This tutorial shows how to do a typical deployment in the Scritpcase. The scriptcase contains two models of application deployment: Typical and Advanced. If you are unsure of how to deploy to a hosting server, watch this video tutorial about ...
    • Installing Scriptcase with PHP 7.3 on Windows

      This documentation will walk you through the steps necessary to install PHP 7.3, Apache 2.4, and Scriptcase manually. When performing this type of installation, you are responsible for configuring your entire environment as well as database ...
    • Request a new license

      Some situations require the reinstallation of Scriptcase, in these cases, the user must generate a new serial on our website to register the tool. Follow the steps below to generate a new serial:  1. Log in to the website The entire process to ...
    • Parallel Installation of Scriptcase

      Never delete the directory where you installed your Scriptcase The procedures in this tutorial, explain only how to install the Scriptcase manually. We recommend to create a backup of your scriptcase before proceeding the update, in Options->Settings ...
    • Hotkeys on Scriptcase

      Scriptcase offers the ability to create shortcuts for the application functionalities. The configuration of each shortcut is simple and the same for all browsers. However the way of use is different, each browser is different, and this is independent ...