mirror of
https://github.com/rsyslog/rsyslog.git
synced 2026-06-19 11:42:55 +02:00
c7ae67aded
Why: Local validation should prevent known workflow traps instead of making each agent rediscover and repair them after a container run. Impact: Local container validation now defaults to host UID ownership, reducing permission cleanup churn in worktrees. Before/After: Before, the helper forced the dev image default user; after, it lets the container wrapper map to the host uid/gid by default. Technical Overview: The local validation helper no longer exports an empty RSYSLOG_CONTAINER_UID for Ubuntu 26.04 check and focused-test lanes. Leaving the variable unset uses the existing devcontainer.sh behavior that passes the host uid/gid to docker and injects passwd/group entries when needed. The container-testing skill now documents this as the normal local mode and keeps RSYSLOG_CONTAINER_UID='' reserved for intentional GitHub Actions user reproduction. The fallback cleanup guidance remains for already-polluted or intentionally CI-user worktrees. With the help of AI-Agents: Codex
This directory contains tools for use by development and CI. The goal is to have a consistent way to do things.
Scripts
-
run-static-analyzer.sh Run the currently approved rsyslog project clang static analyzer.
-
codex-setup.sh Prepare an Ubuntu 24.04 WSL checkout for full rsyslog development. It installs the packages and helper libraries used by the Ubuntu 24.04 development container and can optionally verify a build with the container's RSYSLOG_CONFIGURE_OPTIONS.
-
codex-setup-wsl.ps1 Windows wrapper for running codex-setup.sh inside a WSL distro.
Environment Variables
- RSYSLOG_HOME root of rsyslog sources - e.g. unzipped tarball, git checkout
Files
default_dev_container
Contains the full name of the container to be used for development task if no other is given.
codex-wsl-bootstrap-prompt.md
Copy-paste prompt for asking Codex to set up rsyslog development on a new Windows machine.