Git Product home page Git Product logo

welcome's Introduction

Welcome to the Software Collections Organization

This document offers a comprehensive introduction to the Software Collections Organization (SCLOrg), highlighting the repositories under our umbrella and providing examples of their practical applications, along with links to relevant external resources.

The primary focus of SCLOrg revolves around the Software Collections concept. Software Collections offer a streamlined approach to building, installing, and utilizing multiple software versions on a single system, without disrupting pre-existing system-wide package installation.

In light of recent developments, we have introduced a series of RPMs web development tools. To maximize the utility of these verified packages, we encourage the creation of container images compatible with OpenShift.

Repository Overview

  • Container Contribution Guidelines: Learn about what principles to follow when contributing to the SCLOrg, particularly in relation to container repositories.

  • Container Images Overview Based on Software Collections: Access Dockerfiles, relevant sources, and tests for container images.

  • scl-utils: The upstream project for the scl-utils package available in RHEL, CentOS, and Fedora, enabling the building of RPM packages in an alternative directory.

  • spec2scl: A Python-based tool that facilitates the migration of RPM spec files into SCL-enabled variants by adding macros, scriptlets, and more.

  • SCLOrg: Source code for the SCLOrg website, a Django application that serves as a directory for available Software Collections Organization.

  • centpkg for SCLo: A compact wrapper that assists SCLo SIG maintainers in building SCL packages in CBS.

  • centos-release package: A minimal RPM package with a YUM repository, offering upstream Software Collections built in CBS by the community (excluding those in RHSCL).

  • SCLo CI Tests: Tests executed in CentOS CI to verify the successful (re)building of RPM packages in CBS.

  • RPM List Builder: A tool designed to facilitate the rebuilding of SRPMs in CBS that were previously available in different repositories (e.g., RHSCL and others).

  • RHSCL Container CI: Scripts for testing containers on the RHEL platform.

Orchestrating Containers and PaaS

Kubernetes (commonly referred to as k8s) has emerged as the de-facto standard for orchestrating containers, enabling the large-scale management and configuration of containers as cattle rather than pets. OpenShift is a Platform-as-a-Service (PaaS) built on top of Kubernetes, providing comprehensive application lifecycle management. This includes the ability to quickly build and deploy Docker-formatted containers while managing them on a robust, scalable platform. To learn more about these two technologies, explore the following resources:

Source-to-image

Numerous packages within this organization utilize the source-to-image (s2i) concept, a toolkit and workflow designed for building reproducible Docker images directly from source code. To learn more about source-to-image, you can visit:

welcome's People

Contributors

hhorak avatar lupphes avatar phracek avatar zmiklank avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

welcome's Issues

Where should issues be filed?

The contributor guide does not give a clear indication of how feature requests or bugs should be reported. Many repos in this org seem to have issues that are stale or unmonitored.

Please provide guidance on where issues are being actively triaged and monitored.

ubi8/nodejs-18-minimal (nor its base image) doesn't "useradd" 1001

Container platform

OCP 4, Podman/Docker

Version

ubi8/nodejs-18-minimal

OS version of the container image

RHEL 8

Bugzilla, Jira

No response

Description

The ubi8/nodejs-18-minimal image references USER 1001 but this user does not get created by this image, not in its base image. This is different to the ubi8/nodejs-18 image which uses the uid 1001 which is created in its base image (ubi8/s2i-core). Is there a reason for this, or would it make sense to add this user into the minimal image to ensure similar functionality/experience? Thanks.

Reproducer

No response

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.