Imprimir

Production Environment

We have two types of deployments:

  • Typical
  • Advanced

Production Environment (Typical)

Based on our documentation ( Click Here ), we can configure the production environment below:

1 - On the root of the web server, the folder “TypicalDeploy” was created and in it was extracted the “samples_1.zip”.

Raiz do servidor web Root of the web server

2 - Access the folder /TypicalDeploy (where the applications are stored) from the browser. In it we have the menu application, we’ll access it like this(/TypicalDeploy/menu_scriptcase/menu_scriptcase.php ).

Acesso ao projeto via navegador Project access from the browser

3 - Access the production environment from the browser, by the address your-IP: port/TypicalDeploy/_lib or click the link “Click here to create the connection now”. That’ll be displayed once you access the production environment. On the first access the default password is scriptcase.

 Production Environment access page Production Environment access page

4 - On this page, you’ll be required to set a new password for the production environment for the next time you access it if necessary.

 Password setup for the production environment Password setup for the production environment

5 - You should create a new connection.

 Page to create the database connection Page to create the database connection

6 - You should select the DBMS, that you used in the project.

Page to choose the connection for the production environment Page to choose the connection for the production environment

7 - Inform the database server, on this example, the database is installed in the same machine ad the applications, so we can call it using ‘ localhost ‘, if the database is on another server you can call it by the or IP of the machine, also inform the Username and password (if it exists).

 Page to setup the connection for the production environment Page to setup the connection for the production environment

8 - This step is very important, because we need to inform the same name that was saved at the moment of the deployment (like on step 5). If the name is different than the informed in the deployment, the application will present an error informing that the connection wasn’t successful.

9 - Finally, we should access the project through the browser

Accessing the Project Accessing the Project

Production Environment (Advanced)

Based on our documentation ( Click Here ) we can configure the production environment below:

1 - Folder structure:

 Folder structure of the advanced deploy Folder structure of the advanced deploy

2 - On the root of the web server, the folder “AdvancedDeploy” was created and in it was extracted the “samples_1.zip”.

 Root of the web server Root of the web server

3 - Access the production environment from the browser, by the address your-IP: port/AdvancedDeploy or click the link “Click here to create the connection now”. That’ll be displayed once you access the production environment. On the first access the default password is scriptcase.

Production Environment access page Production Environment access page

4 - On this page, you’ll be required to set a new password for the production environment for the next time you access it if necessary.

Password setup for the production environment Password setup for the production environment

5 - You should create a new connection.

 Page to create the database connection Page to create the database connection

6 - You should select the DBMS, that you used in the project.

 Page to choose the connection for the production environment Page to choose the connection for the production environment

7 - Inform the database server, on this example, the database is installed in the same machine ad the applications, so we can call it using ‘ localhost ‘, if the database is on another server you can call it by the or IP of the machine, also inform the Username and password (if it exists).

 Page to setup the connection for the production environment Page to setup the connection for the production environment

8 - This step is very important, because we need to inform the same name that was saved at the moment of the deployment (like on step 5). If the name is different than the informed in the deployment, the application will present an error informing that the connection wasn’t successful.

9 - Finally, we should access the project through the browser

 Accessing the Project Accessing the Project