Parallel Installation of Scriptcase on Windows, Linux, and macOS

Parallel installation can be performed on Windows, Linux, and macOS, provided that the environment meets the requirements to run the Scriptcase version being installed.

This type of installation allows you to maintain two or more Scriptcase installations on the same web server. This procedure is useful for testing new Scriptcase versions and new features without modifying your actual development environment.

In this tutorial, you will learn how to perform a parallel installation of Scriptcase on Windows, Linux, and macOS, using a similar procedure for all three operating systems.

Before you begin

To perform a parallel installation, Scriptcase must already be installed and running in the environment. The new installation will be added to the same web server, using a different directory from the existing installation.

Important:

• Do not delete the existing installation folder.

• Verify that the PHP version used in the environment is compatible with the Scriptcase version to be installed.

• Go to the official Scriptcase download page and download the compressed package of the version you want to install. Verify that the selected package is compatible with the PHP version available in the environment.

Important: For this procedure, use the compressed Scriptcase package, not the automatic installer.

1. Back up the current installation

Although the parallel installation procedure does not modify the files, projects, or settings of the current Scriptcase installation, you can create a backup before starting if you want additional security.

To do this:

1. Access Scriptcase.

2. From the main menu, go to Settings > Administration.

3. In the sidebar, select Services > Backup.

4. Generate the backup and download the file.

5. Store the file in a safe location.

2. Locate the web server directory

Before preparing the new installation, you need to identify the directory where the current Scriptcase installation is located.

The paths shown below are examples based on standard installations performed using the official Scriptcase installer. They may vary depending on the installed version, operating system, and environment settings.

If you use a manual or customized installation, locate the web server directory where Scriptcase is installed.

The new installation must be added to the same web directory as the current installation, using a different folder.

Attention: Do not delete, rename, or replace the directory of the existing Scriptcase installation.

3. Extract and prepare the files

After completing the download, you will need to extract and prepare the files for the new installation.

1. Locate the compressed Scriptcase file.

2. Extract its contents to a temporary directory of your choice.

3. Identify the folder created during extraction.

4. Rename this folder to a name different from the one used by the current installation.

For example, if the existing installation uses the scriptcase folder, you can rename the new folder to scriptcase_teste.

Important: The new folder name must be different from the one used by the current installation to avoid replacing files.

4. Copy the new installation to the web server

After preparing the files, copy the scriptcase_teste folder to the directory identified in step 3.

The new folder must be at the same level as the folder used by the current installation.

For example, the final structure will look similar to this:

The procedure can be performed using the operating system interface or the terminal, as shown in the examples below.

Windows

Using File Explorer:

1. Locate the scriptcase_teste folder prepared in the previous step.

2. Copy the folder.

3. Access the directory identified in step 3.

4. Paste the folder into that location.

Example of the final path:

C:\Program Files\NetMake\v10-php82\wwwroot\scriptcase_teste\

Linux

On Linux, the folder can be copied using the file manager or the terminal.

To copy the new installation using the terminal, run:

sudo cp -a /caminho/scriptcase_teste /opt/NetMake/v10-php82/wwwroot/

Replace /caminho/scriptcase_teste with the location of the extracted folder and adjust the destination directory according to your installation.

After copying, verify that the user responsible for the web server has the necessary permissions to access the files and write to the directories required by Scriptcase.

macOS

On macOS, use Finder to copy the scriptcase_teste folder to the web directory corresponding to the current installation.

You can also perform the procedure using the terminal:

sudo cp -R /caminho/scriptcase_teste Applications/Scriptcase/v10-php82/wwwroot/

Replace the paths with the directories corresponding to your environment.

After copying, verify the access permissions for the files and directories of the new installation.

Note: It is not necessary to stop Apache just to copy the files of the new installation, provided that no server configuration is changed.

5. Access the new Scriptcase installation

After copying the files, open your browser and access the new installation.

To do this, use the same address and port as the current installation, changing only the directory name.

For example:

Current installation:

http://127.0.0.1:8095/scriptcase/

New installation:

http://127.0.0.1:8095/scriptcase_teste/

Note: The addresses and port 8095 are examples only. Use the address and port configured in your environment.

When accessing the new installation for the first time, the Scriptcase installation wizard will be displayed.

6. Configure the new installation

In the installation wizard, follow the instructions displayed on the screen to configure the new environment.

1. Select the desired language.

2. Verify the environment requirements and the necessary PHP extensions.

3. Choose the installation type.

4. Configure the information requested by the wizard.

5. Set the administrator username and password when prompted.

6. Complete the installation.

If you use the custom installation, you will need to configure the database used by Scriptcase. In this case, use a database exclusively for the new installation.

7. Verify that both installations are working

After completing the configuration, access both installations separately.