The delivery of Connect for includes one or more .tar.gz archive(s) and the shell script "install-connect.sh", which largely automates the installation process. The installation script has been tested for the following Linux distributions, but should also work with other common Linux distributions:
CentOS 8
CentOS 9
Debian 11
Fedora 35
RedHat Enterprise Linux 8.5
SUSE Linux Enterprise Server 15 SP3 (SLES)
Ubuntu 20.04.4 LTS
Preparations
Special
...
considerations for installation on CentOS, Fedora or RedHat
We recommend to install installing the package 'sudo' already before starting the installation. Proceed as follows:
...
If this package is not installed, the installation of this package is performed by the installation script. In this case, the user who runs this script must have the necessary permissions to install the package.
...
During the installation of Connect, individual Linux components may need to be installed later. Therefore, even before you start starting the installation process, make sure that there are no reasons not to install these components.
Linux Distribution | Additionally required components |
|---|---|
CentOS | sudo |
Debian | libicu-dev |
Fedora | sudo |
RedHat Enterprise Linux | sudo |
SUSE Linux Enterprise Server | - |
Ubuntu | - |
Also, check the prepare_os function in the installation script to make sure that it does not perform any unwanted configuration operations.
...
Log in to the desired system with a user with administrator privileges and copy the installation files (GalileoGroup.Connect.*.tar.gz / install-connect.sh) to a directory. Change with cd Use the cd command to change to this directory and , then start the installation with the following command line:
| Code Block |
|---|
. ./install-connctconnect.sh |
Now follow the instructions of the script to perform the installation. The steps required for this depend on the Linux distribution, the Connect components to be installed, and the packages already present. The rough sequence is as follows:
You will be prompted (by sudo) to enter your password in order to perform administrative tasks.
You are prompted to enter the user under whose ID Connect is to be installed. If this user does not exist, it will be created. It is possible to enter your own user
...
id, but this procedure is not recommended for productive environments.
The archives to be installed are analyzed. If they do not contain the .NET Framework, you will be asked to enter the installation location of the .NET Framework to be used. You also have the option of installing your own dedicated .NET Framework, but note that this should also be kept up to date
...
regarding security patches.
The archives to be installed are installed.
Any shell scripts required for administration are now generated.
The initial configuration is generated (if not already available).
Finally, a quick start guide for starting and stopping Connect using the scripts generated during installation is displayed.
Uninstall
The following steps are necessary for complete uninstallation:
...
Delete the connect directory in the home directory of the connect user
Delete the .dotnet directory in the home directory of the Connect user (if it exists)
...
...
Delete the Connect user if it is no longer needed