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 longer.
3. Access to the database that will use the project after it is deployed;
Starting the advanced 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", Caso escolha a opção "Selecionar Aplicações", 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 "Advanced".
Step 3: Later create a template of publication for the settings are saved and set can be reused.
Step 4: Set the directory structure of the production environment according to the structure of common libraries defined on the production server. Under two separate configuration examples are shown.
Note: It is necessary to create a directory on your production server, so that houses all the production environment (Common Libraries) publication, noting that in the documents directory must inform the absolute path to the folder .. In this example we are using the directory production.
Note: In this example it is necessary to create a directory of images, documents and temp files in your production server, remembering that in the documents directory must inform the absolute path to the folder. Regarding the Production Environment (Common Library), you must take the "prod" folder generated at the end of this publication. In this case we are using separate directories from the previous example.
Note: In both examples above, if you want after the completion of the publication process, are available, in addition to link the project, the link of the production environment (Common Libraries), check the "Post to common files (css, buttons, images, messages) ".
Directory of the Production: Set of libraries and services used by applications published. Set here the path relative to the prod directory, ej: /production/prod or /prod
Directory of the Images (used in the upload process): Folder where the images are saved when some application uses a field of type "image (file name)". Enter this option and the relative path to the img directory, ej: /production/file/img
Directory Temporary: Folder will be created where the temporary files created during the execution of applications. Files in this directory are removed periodically based setting specifies, by default is 120 minutes. Use this field the path relative to the tmp directory, ej: /production/tmp or /temp_files/tmp
Directory of the Documents (used in the upload process): Folder where you saved the documents, when some application uses a field of type "Document (file name)". Absolute path (full path) to the doc directory, ej: C:/Apache/htdocs/production/file/doc or C:/Apache/htdocs/my_documents/doc
Note: The Character "/" means the root of the Web server, is used for relative paths.
Step 5: Set the name of the connection with the database, which will be used in the project after it is published.
Step 6: Choose the mode of publication to be used. ScriptCase offers three options:
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 7: At the end of the process the applications published a report along with the links to download both the project as the common libraries, which are necessary for the execution of applications in production routines will be displayed, so it is mandatory that they be taken together the publishing package.
Note: With the advanced publication is necessary to download the "Production Environment", which corresponds to all the files responsible for public libraries. If you do not wish to download the Production Environment (Common Libraries) generated by the link after publication, you can choose to download it here. If you want to publish the same project again, no need to download the common libraries. This information is not only valid when ordinary libraries have been updated to a new release of ScriptCase.
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 "AdvancedDeployment" and inside of her was extracted the "samples_3.zip”.
This other picture we can see that:
Accessed by browser /ADvancedDeployment ( in that case is the folder where the applications are). Inside there is a form application, we will access it(/AdvancedDeployment/form01/form01.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 /prod_scriptcase/_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.