Suporte e atendimento

In order for our content management application to be able to operate on an internal and restricted network, with an estimated capacity of up to 50 licenses, it is recommended that a local server with the following specifications be available:

• Red Hat 9.x operating system (latest version available) (subscription required) / AlmaLinux 9.x (latest version available)
• Processor with 4 CPU cores;
• 4 GB memory;
• 250 GB disk/storage.

From 51 to 250 licenses, it is recommended to have a local server with the following specifications:

• Red Hat 9.x operating system (latest version available) (subscription required) / AlmaLinux 9.x (latest version available)
• Processor with 8 CPU cores;
• 8 GB memory;
• 500 GB disk/storage.

For more than 251 licenses, our technical team must assess the necessary configuration.

To install the server on the internal network, remote/VPN access must be provided so that the installation can be performed, in addition to "root" access on the server.

In addition to the server being available, a certificate (CSR) must also be provided. OWASP (Open Web Application Security Project) recommends the use of authenticated encryption, secure protocols, and adequate key management to protect sensitive data.

When using a certificate, it is mandatory to have a FQDN (Fully Qualified Domain Name) to assign and configure on the server, without being in the .local TLD (Top-Level Domain) to use the SSL/TLS certificate from a public and trusted Certificate Authority (CA).

OWASP (Open Web Application Security Project) is a non-profit organization that aims to improve software security. It is a global community that works together to promote the security of web applications.

FQDN (Fully Qualified Domain Name) is a complete domain name that identifies the location of a device or service on the Internet. It is also known as an absolute domain name.

TLD stands for "Top-Level Domain", which means top-level domain or top-level domain. It is the domain extension that appears after the last dot of an Internet address. For example, in the domain "google.com", ".com" is the TLD.

In order to synchronize the clocks of the terminals on a network without internet access, an internal NTP server or access to an external one is required for the application to function properly.

Required input ports on the server:

• 443
• 22

In order to proceed with the installation and configuration of the server, the machine must have full internet access during the installation procedure, enabling all necessary downloads and configurations.
Additionally, we need access to the address staging.worldvds.com on port 22 to install the software. After this process, the appropriate network restrictions can be applied and additional URLs relevant to the project can be authorized later:

It can be made available on either port 80 or port 443.

- If port 443 is used, a valid certificate must be provided, preferably not self-signe.
- If the certificate is self-signed, all devices will have to be updated with the new certificate, which may result in incompatibilitie.

You will also need to ensure the following items:

• SSH and HTTP(S) access to the server
• User with root permissions
• Unrestricted access to the internet, at least at the time of installation
• Access to the following extra repositories:

  1. crb

  2. epel

  3. influxdata

  4. remi-modular

  5. remi-safe

  6. rpmfusion-free-updates

  7. rpmfusion-nonfree-updates

To keep the server up to date, access to the repositories must remain free even after installation.

For the server to have external access and/or integrations, the following URLs will need to be released:

Click here to access this content in portuguese.