Linux workstation

Upstream software project

rmt-server

Ansible playbook for RMT deployment

About rmt-server

Ansible playbook for RMT deployment

This project links 1 native package record across 1 recorded operating-system release. Compare the retained versions and architectures below, then open the package for your own release.

These are catalog observations, not a guarantee of installation, compatibility, or upstream support.

Visit project website

Project pictures and package coverage

rmt-server repository preview from GitHub
Project repository preview, supplied by GitHub. Open source repository
openSUSE Leap 16.0: 1 package records. Catalog coverage diagram, not an application screenshot.rmt-server: recorded package coverageopenSUSE Leap 16.01 records
OpenFactory diagram of linked package records. It is not an application screenshot.

Project identity

Project
rmt-server
Publisher
Not authoritatively mapped
Native package records
1
Operating systems
opensuse-leap-16-0
License expression
GPL-2.0-or-later
Metadata completeness
100/100 (not a software quality rating)
Homepage
Visit upstream site
Source repository
Open source repository

Source-reported description

The fullest retained description is shown with its source. Distribution packaging descriptions may include downstream details.

Ansible playbook and roles for automated deployment and configuration of RMT server. Includes SSL certificate generation, database setup, and nginx configuration.

Description source

Packages by operating system

Compare recorded versions, then open a package for dependency, file, checksum, and repository evidence. Version strings are distribution-specific, not a ranking of newer software.

openSUSE Leap 16.0

  1. ansible-rmt-server

    openSUSE Leap 16.0 / Development/Tools/Other / source rmt-server

    3.0.0-160000.1.1

    Ansible playbook for RMT deployment

    noarchleap-16.0

Project resources and further reading

Mapping provenance

Only source-backed identity signals create public cross-OS links. A reviewer can later approve or dispute an inferred relationship without rewriting native package history.

No field-level source record is published yet.