This tutorial shows how do a typical deployment in the Scritpcase. The scriptcase contains two models of application deployment:
Typical and Advanced.
If you have questions about which deployment best suits your needs, read the initial tutorial about deployment here.
1. Web server (eg: Apache, IIS)
2. PHP version 5.4 or later.
3. Access to the database that will use the project after it is deployed;
Starting the typical deployment process:
This type of publication is intended for users who want to use the default configuration of the production environment (Common Libraries), its configuration is done automatically by Scriptcase. The process described below:
Step 1: Access your project and choose the option "Project -> Deploy", available in the top menu.
After click in Deploy, you have the option to deploy all project applications or choose which will be deployed. In this tutorial we will use the option "All".
Note: Case you choose the option "Select Applications", a screen with all project applications will be displayed so you can choose only those that will be deployed.
Step 2: In the next screen, choose which type of publicacion you want to use, for this examples we will choose the "Typical".
Step 3: In the next screen, choose which will be the initial application.
It is necessary to leave checked the common libraries option, which corresponds to all the files responsible for "Production Environment". You must also leave the option labeled common files, so that images, css and custom messages to be sent at the time of generation of the deployment.
1 - Generate the ZIP with the applications (recommended): At the end of the process will be provided a link to download the publication package.
Note: This option is recommended for being the least depends on other services to be made.
2 - Deployment in the directory on the server: Deploy the applications in the directory informed. This option should only be used if the publication is made in the same server where the ScriptCase is installed, otherwise the option will not be valid..
3 - Deploy in the FTP server: Automatically deploy the applications on a remote FTP server.
Note: To use this option it is necessary to have a server that disponibile FTP access and a user with write permissions in the same folder.
FTP server: Server which will be used to publish the project. Insert here the domain of your FTP server.
User: FTP user of the production server, remembering that this user must have write permission in the server folder, otherwise it will not work.
Password: Password of the FTP user.
Directory in the FTP: Directory of the chosen server for deploy the project..
Step 4: At the end of process will be display an report of the deployed applications with the link to download the project.
Starting the process of creation of the Production Environment:
The next step is to unzip and extract the files of the zip generated by ScriptCase.
In the example the structure is according with the image below:
In the root (wwwroot, in the case of example) of the web server was created a folder called "TypicalDeployment" and inside of her was extracted the "samples_2.zip”.
This other picture we can see that:
Accessed by browser /TypicalDeployment ( in that case is the folder where the applications are). Inside there is a menu application, we will access it(/TypicalDeployment/menu_scriptcase/menu_scriptcase.php ).
This will be the error displayed, when don't have the connection created.
In the next step, we will create the connection that applications use to not be shown any more error and work correctly.
Step 1: Access by the browser the ' prod ' by address /TypicalDeployment/_lib or click in link "Click here to create the connection now". This screen will be shown as the image below. On first access the default password is scriptcase.
On the next screen you will be prompted for a new password when you need to access the "prod" again.
Step 2: We will create a new connection.
Step 3: In this step we chose the DBMS, the database that we use in the application.
Step 4: Inform the Server Database, as our database is on the same machine applications, we can call via localhost if the database is on another server can be called via machine name or IP number, inform also the Login and Password to access the database (if any).
Step 5: This step is very important because we need to inform the same name that was entered at the time of publication (as we see in Step 2 from Step 2). If you different from what was reported in the publication name, the application will display an error regarding database.
Step 6: The last step will be accessing the application browser.