raynetgmbh/raynet-one-backend repository overview

⁠Raynet One

⁠The all-in-one data management platform for your IT environment

Raynet One is available online and accessible from every desktop or mobile device which is connected to it via relevant Docker containers. The platform serves to cover greater parts of data management processes in your IT environment. Functions include automated or manual inventory and discovery runs, vulnerability detection, deep-dive inspections of IT assets and the normalized and enriched display of available data.

⁠Getting Started (cloud-based usage)

These instructions describe the prerequisites and processes which are necessary to access and use the Raynet One platform in a cloud environment.

For this cloud-based solution, setting up or configurating the platform or any of its Docker components is neither possible nor necessary for end-users. You'll receive a link with your credentials and can start exploring Raynet One right away. Nonetheless, there are some prerequisites and requirements that your system has to fulfil. Also for Windows and MacOS, make sure to use Linux Containers, WSL2 is recommended.

⁠Prerequisites for platform access

In order to operate with the platform, the environment must be able to run Linux docker containers.Example deployment templates will be also available.

• Windows⁠
• OS X⁠
• Linux⁠

⁠Prerequisites for Windows and Non-Windows runners

Windows runner installation:

OS: Windows 10 x64 or higher, Windows Server and Windows Server Core 2012 x64 or higher, Nano Server Version 1808 x64 or higher. Microsoft dotnet runtime or ASP.NET Core hosting bundle package 8.0 or greater must be installed (download here: https://dotnet.microsoft.com/en-us/download/dotnet/8.0⁠).

Non-Windows runner installation:

The environment must be able to run Linux docker containers because Non-Windows runners are only available as Linux docker images.

⁠Getting Started (on-prem settings)

These instructions describe the prerequisites and processes which are necessary to access and use the Raynet One platform in an on-prem environment.

⁠Docker containers which Raynet One relies on

The default configuration consists of eight containers:

• scheduler,
• frontend,
• runner,
• backend,
• minio-1 blob storage,
• database powered by SQL,
• staging-1 based on mongoDB,
• rabbitmq3-1 messaging queue,
• vault: secret provider,
• keycloak: identity provider.

⁠Installation with docker-compose

The easiest way to run the image with reasonable default is to use docker-compose command. You find the Raynet One YML files as templates here:

[list with links to YML files]

⁠Environment variables to be adapted for on-prem usage

Generally, it is also possible to use Raynet One as an on-prem platform. In this case, YML files serve as templates to configure your environment. Therefore, you must adapt a number of variables as listed below.

⁠For SQL DB connection:

SystemDatabaseConfig__ConnectionStrings__System

⁠For blob storage settings:

Storage__MinIoConfiguration__MinIOEndpoint: Storage__MinIoConfiguration__MinIOAccessKey: Storage__MinIoConfiguration__MinIOSecretKey: Storage__MinIoConfiguration__BucketName:

⁠For MongoDB settings:

StagingDatabaseConfig__Host: staging StagingDatabaseConfig__Port: StagingDatabaseConfig__AuthDatabase: StagingDatabaseConfig__UserName: StagingDatabaseConfig__Password: StagingDatabaseConfig__Database:

⁠Secret provider settings

SecretsProviderConfig__Provider: HashiCorpVault SecretsProviderConfig__HashiCorpVaultConfig__Url: SecretsProviderConfig__HashiCorpVaultConfig__AuthMethod: SecretsProviderConfig__HashiCorpVaultConfig__Secret:

⁠Health monitoring settings

ServiceHealthMonitorig__Backend__hostname: ServiceHealthMonitorig__Backend__port: ServiceHealthMonitorig__Backend__protocol: ServiceHealthMonitorig__Scheduler__hostname: ServiceHealthMonitorig__Scheduler__port: ServiceHealthMonitorig__Scheduler__protocol:

⁠Catalog related settings

Catalog__Url: https://rayventorycatalog.raynet.de⁠: Catalog__ApiKey: Catalog_MaxAttempts:

⁠License Management

LicenseConfig__Type: OrderNumber LicenseConfig__OrderNumber: LicenseConfig__Company: LicenseConfig__Email: LicenseConfig__User: LicenseConfig__EmailActivation: LicenseConfig__FilePath:

⁠Find Us

• Raynet GmbH corporate website⁠
• Raynet EALM GitHub⁠