$ account opsre
This repository is a curated awesome-list of open-source operations and DevOps tools, organized into 82 categories with 653 entries. It is not a software application; it is a structured dataset of YAML metadata files that are transformed into bilingual README tables via a GitHub Action using Go templates. The data lineage is: contributors add YAML files under items/<category>/<tool>.yaml with fields kind, owner, repo, desc, and desc_en; on push to main, the generator workflow runs the eryajf/yaml-readme action to fetch live GitHub metadata (license, stars, creation/update dates) and render README.md and resources/README-en.md from the provided templates. The repository serves as a discovery resource for engineers evaluating ops tools, answering questions like 'what are the best open-source tools for a given ops category?' and 'what is the license, star count, and last update of a tool?'. It is actively maintained with recent commits, a YAML linting CI, and a clear contribution guide. The reusable assets are the templating pattern and CI workflows, which can be adapted to any curated list or structured-data-to-document pipeline.
LiteOps is a lightweight, self-hosted CI/CD platform built with Django 4.2 (Python 3.9) and Vue 3 (Ant Design Vue). It provides project management, build task configuration, credential storage (GitLab tokens, SSH keys, kubeconfig), environment management, and notification robots (DingTalk, WeChat, Feishu). Builds are executed inside a Docker-in-Docker container that includes Java, Maven, Node, and kubectl, with real-time log streaming via Server-Sent Events (SSE). The system integrates with GitLab for webhook-triggered builds and branch/commit information, supports LDAP authentication, and enforces role-based permissions (function and data scopes). The frontend dashboard displays build statistics, trends, and recent builds using ECharts. The codebase is functional and actively developed, but exhibits several engineering weaknesses: no automated tests, threading for async build execution (no task queue), hardcoded secrets (admin password, database credentials), SHA256 password hashing (not bcrypt), and plaintext storage of GitLab tokens. The Docker image is large and requires privileged mode. Despite these issues, the system is suitable for small teams needing a simple, integrated CI/CD solution without external dependencies beyond GitLab and MySQL.