hexrift 0.1.0__tar.gz

hexrift-0.1.0/.github/CODEOWNERS

@@ -0,0 +1 @@
+* @wlix13

hexrift-0.1.0/.github/CONTRIBUTING.md

@@ -0,0 +1,104 @@
+# Contribution Guidelines
+
+First of all, thank you for your interest in the project.
+
+Regardless of whether you are thinking about creating an issue or opening a pull request, I truly appreciate the help.
+Without communication, I cannot know what the community wants, what they use or how they use it.
+Pull requests and issues are exactly what gives me the visibility I need, so thank you.
+
+## Getting started
+
+While following the exact process is neither mandatory nor enforced, it is recommended to try following it as it may help avoid wasted efforts.
+
+### Creating an issue
+
+Whether you have a **question**, found a **bug**, would like to see a **new feature** added or anything along those lines, creating an issue is
+going to be the first step. The issue templates will help guide you, but simply creating an issue with the reason for the creation
+of said issue is perfectly fine.
+
+Furthermore, if you don't want to fix the problem or implement the feature yourself, that's completely fine.
+Creating an issue alone will give both the maintainers as well as the other members of the community visibility on said issue,
+which is a lot more likely to get the issue resolved than if the problem/request was left untold.
+
+### Solving an issue
+
+Looking to contribute? Awesome! Look through the open issues in the repository, preferably those that are already labelled.
+
+If you found one that interests you, try to make sure nobody's already working on it.
+Adding a comment to the issue asking the maintainer if you can tackle it is a perfectly acceptable way of doing that!
+
+If there's no issue yet for what you want to solve, start by [Creating an issue](#creating-an-issue), specify
+you'd like to take a shot at solving it, and finally, wait for the maintainer to comment on the issue.
+
+You don't _have_ to wait for the maintainer to comment on the issue before starting to work on it if you're sure that there's no other
+similar existing issues, open or closed, but if the maintainer has commented, it means the maintainer has, based on the comment itself,
+acknowledged the issue.
+
+## Development Setup
+
+### Package Management
+
+This project **only** supports the `uv` installation method. Other tools, such as `conda`
+or `pip`, don't provide any guarantees that they will install the correct
+dependency versions. You will almost certainly have _random bugs, error messages,_, and other problems if you don't use `uv`.
+Please _do not report any issues_ if you use non-standard installations, since almost all such issues are invalid.
+
+Furthermore, `uv` is [up to 115x faster](https://github.com/astral-sh/uv/blob/main/BENCHMARKS.md)
+than `pip`, which is another _great_ reason to embrace the new industry-standard
+for Python project management.
+
+**Quick & Easy Installation Method:**
+
+There are many convenient ways to install the uv command on your computer. Please check the link below to see all options.
+
+[Installation Guide](https://docs.astral.sh/uv/getting-started/installation/)
+
+Alternatively, if you want a very quick and easy method, you can install it as follows:
+
+```bash
+pip install -U uv
+```
+
+### Pre-commit Hooks (via prek)
+
+This project uses pre-commit hooks to ensure code quality and consistency. Before making any commits, please install and set up prek:
+
+```bash
+# Install prek (if not already installed)
+uv tool install prek
+# or use with uv run (as dev environment already has it covered)
+uv run prek
+
+# Install the pre-commit hooks
+prek install
+```
+
+The pre-commit hooks will automatically run on each commit to check for:
+
+- Code formatting
+- Linting issues
+- Other quality checks
+
+If any hooks fail, please fix the issues before committing. You can manually run all hooks with:
+
+```bash
+prek run --all-files
+```
+
+## Commits
+
+All commits are expected to follow the conventional commits specification.
+
+```text
+<type>[scope]: <description>
+```
+
+It's not a really big deal if you don't, but the commits in your PR might be squashed into a single commit
+with the appropriate format at the reviewer's discretion.
+
+Here's a few examples of good commit messages:
+
+- `feat(api): Add endpoint to retrieve images`
+- `fix(alerting): Remove bad parameter from Slack alerting provider`
+- `test(security): Add tests for basic auth with bcrypt`
+- `docs: Add paragraph on running the application locally`

hexrift-0.1.0/.github/ISSUE_TEMPLATE/BUG-REPORT.yaml

@@ -0,0 +1,49 @@
+name: "Bug report"
+description: "Found something that's not working as expected? Provide detailed information about the issue to help get it resolved."
+labels:
+  - bug
+
+body:
+  - id: description
+    type: textarea
+    validations:
+      required: true
+    attributes:
+      label: "Describe the bug"
+      description: "Tell what went wrong and how it's affecting your work."
+
+  - id: what-you-see
+    type: textarea
+    attributes:
+      label: "What do you see?"
+      description: "Share what's actually happening - error messages, unexpected behavior, or missing functionality. Screenshots are welcome!"
+
+  - id: what-you-expect
+    type: textarea
+    attributes:
+      label: "What do you expect to see?"
+      description: "Describe the intended behavior - what should have happened instead?"
+
+  - id: steps-to-reproduce
+    type: textarea
+    validations:
+      required: false
+    attributes:
+      label: "List the steps that must be taken to reproduce this issue"
+      description: "Provide exact steps to recreate this bug. Include any code snippets, configuration files, or commands used. The easier it is to reproduce, the quicker it can be fixed!"
+      placeholder: |
+        1. Start the application
+        2. Navigate to localhost:8080/metrics
+        3. No metrics are displayed
+
+  - id: version
+    type: input
+    attributes:
+      label: "Version"
+      description: "Which version of the project are you using? (check package.json, tags, or release notes if unsure)"
+
+  - id: additional-information
+    type: textarea
+    attributes:
+      label: "Additional information"
+      description: "Anything else that might help solve this? Environment details, related issues, or workarounds you've tried."

hexrift-0.1.0/.github/ISSUE_TEMPLATE/FEATURE-REQUEST.yaml

@@ -0,0 +1,31 @@
+name: "Feature request"
+description: "Have an idea that could improve this project? Share your suggestion and help shape the future development."
+labels:
+  - feature
+
+body:
+  - id: description
+    type: textarea
+    validations:
+      required: true
+    attributes:
+      label: "Describe the feature request"
+      description: "Describe the feature or improvement you'd like to see. Be as specific as possible about what it should do and how it should work."
+
+  - id: reason
+    type: textarea
+    attributes:
+      label: "Why would this feature be valuable?"
+      description: "Explain the problem this feature would solve or the benefit it would provide. Include use cases or scenarios where this would be helpful."
+
+  - id: usage-duration
+    type: input
+    attributes:
+      label: "How long have you been using this project?"
+      description: "This helps provide context for your request. Feel free to skip if you prefer not to answer."
+
+  - id: additional-information
+    type: textarea
+    attributes:
+      label: "Additional information"
+      description: "Any other details that might be relevant? Similar features in other tools, implementation ideas, or potential challenges to consider."

hexrift-0.1.0/.github/ISSUE_TEMPLATE/config.yaml

@@ -0,0 +1 @@
+blank_issues_enabled: false

hexrift-0.1.0/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,75 @@
+## Pull request type
+
+<!-- Please check ONE that best describes this PR -->
+
+- [ ] 🐛 **Bug fix** (fixes an issue with deployment or configuration)
+- [ ] ✨ **New feature** (adds new deployment capability or server configuration)
+- [ ] 🔄 **Enhancement** (improves existing deployment or infrastructure setup)
+- [ ] 🏗️ **Infrastructure** (changes to server configuration or infrastructure)
+- [ ] 🚀 **Deployment** (updates to deployment automation or processes)
+- [ ] 📝 **Documentation** (updates to deployment guides or configuration docs)
+- [ ] 🔒 **Security** (security improvements to server configuration)
+- [ ] 📦 **Dependencies** (updates to pyinfra or other dependencies)
+
+## Description
+
+### What does this PR do?
+
+<!-- Provide a clear and concise description of what this PR accomplishes -->
+
+### Why is this change needed?
+
+<!-- Explain the motivation and context for this change -->
+
+### Related Issues
+
+<!-- Link to related issues using "Fixes #123", "Closes #123", or "Relates to #123" -->
+
+## Changes Made
+
+<!-- Describe the changes you made. Use bullet points for clarity -->
+
+-
+-
+-
+
+## Testing
+
+<!-- Describe how you tested your changes -->
+
+- [ ] Tested deployment on development server
+- [ ] Verified configuration changes work as expected
+- [ ] No testing required (documentation changes only)
+
+## Checklist
+
+<!-- Ensure all applicable items are completed before requesting review -->
+
+- [ ] Code follows project style guidelines
+- [ ] Self-review completed
+- [ ] Deployment tested on development environment
+- [ ] Documentation updated (if applicable)
+- [ ] No linter errors
+
+## Security Considerations (if applicable)
+
+<!-- Include if your changes have security implications -->
+
+- [ ] Security improvement
+- [ ] No security impact
+- [ ] Potential security risk (explain below)
+
+## Additional Context
+
+<!-- Any other information that might be helpful for reviewers -->
+
+---
+
+<!--
+Reminder: Please ensure your PR:
+- Has a descriptive title
+- Addresses a single concern
+- Is based on the latest main branch
+- Has been tested in a development environment
+- Updates documentation as needed
+-->

hexrift-0.1.0/.github/dependabot.yml

@@ -0,0 +1,19 @@
+version: 2
+updates:
+  - package-ecosystem: "github-actions"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    groups:
+      actions:
+        patterns:
+          - "*"
+
+  - package-ecosystem: "pip"
+    directory: "/"
+    schedule:
+      interval: "weekly"
+    groups:
+      python-deps:
+        patterns:
+          - "*"

hexrift-0.1.0/.github/labels.yaml

@@ -0,0 +1,95 @@
+# Core Labels
+- name: "bug"
+  description: "Something is not working"
+  color: "d73a4a"
+
+- name: "feature"
+  description: "New feature or request"
+  color: "a2eeef"
+
+- name: "enhancement"
+  description: "Improvement to existing functionality"
+  color: "a2eeef"
+
+- name: "docs"
+  description: "Documentation updates"
+  color: "0075ca"
+
+- name: "breaking-change"
+  description: "Breaking changes"
+  color: "b60205"
+
+- name: "core"
+  description: "Core & Architecture changes"
+  color: "006b75"
+
+- name: "security"
+  description: "Security-related changes"
+  color: "ee0701"
+
+- name: "refactor"
+  description: "Code refactoring"
+  color: "cccccc"
+
+- name: "cli"
+  description: "CLI & Commands"
+  color: "f9d0c4"
+
+- name: "templates"
+  description: "Templates updates"
+  color: "c2e0c6"
+
+- name: "tests"
+  description: "Testing"
+  color: "e99695"
+
+- name: "ci-cd"
+  description: "CI/CD and automation"
+  color: "0052cc"
+
+- name: "dependencies"
+  description: "Changes to dependencies"
+  color: "a569bd"
+
+# PR Labels
+- name: "duplicate"
+  description: "This issue or PR already exists"
+  color: "cfd3d7"
+
+- name: "invalid"
+  description: "This doesn't seem right"
+  color: "e4e669"
+
+- name: "wontfix"
+  description: "This will not be worked on"
+  color: "ffffff"
+
+- name: "skip-changelog"
+  description: "Exclude from changelog"
+  color: "d4c5f9"
+
+# Status Labels
+- name: "needs review"
+  description: "Pull request needs code review"
+  color: "fbca04"
+
+- name: "ready to merge"
+  description: "Pull request is approved and ready to merge"
+  color: "0e8a16"
+
+- name: "in progress"
+  description: "Work is currently in progress"
+  color: "ededed"
+
+# Priority Labels
+- name: "priority: high"
+  description: "High priority issue or PR"
+  color: "d93f0b"
+
+- name: "priority: medium"
+  description: "Medium priority issue or PR"
+  color: "fbca04"
+
+- name: "priority: low"
+  description: "Low priority issue or PR"
+  color: "0e8a16"

hexrift-0.1.0/.github/release.yaml

@@ -0,0 +1,49 @@
+changelog:
+  exclude:
+    labels:
+      - duplicate
+      - invalid
+      - wontfix
+      - skip-changelog
+    authors:
+      - dependabot
+      - dependabot[bot]
+      - github-actions[bot]
+      - renovate[bot]
+
+  categories:
+    - title: 💥 Breaking Changes
+      labels:
+        - breaking-change
+    - title: ✨ Features & Enhancements
+      labels:
+        - feature
+        - enhancement
+    - title: 🐛 Bug Fixes
+      labels:
+        - bug
+    - title: 🏗️ Core & Architecture
+      labels:
+        - core
+        - refactor
+    - title: ⚙️ CLI & Commands
+      labels:
+        - cli
+    - title: 📝 Templates
+      labels:
+        - templates
+    - title: 🔧 CI
+      labels:
+        - ci-cd
+    - title: 📚 Documentation
+      labels:
+        - docs
+    - title: 📦 Dependencies
+      labels:
+        - dependencies
+    - title: 🧪 Testing
+      labels:
+        - tests
+    - title: 📝 Other
+      labels:
+        - "*"

hexrift-0.1.0/.github/workflows/check-commit-message-pr.yaml

@@ -0,0 +1,87 @@
+name: 🔍 Check commit message in PR
+
+on:
+  pull_request:
+    types:
+      - opened
+      - edited
+      - reopened
+      - synchronize
+
+jobs:
+  check-commit-message:
+    name: 🔍 Check commit message in PR
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v6
+        with:
+          ref: ${{ github.event.pull_request.head.sha }}
+
+      - name: Check for fixup commits
+        uses: gsactions/commit-message-checker@v2
+        with:
+          pattern: "^(?!fixup!).*$"
+          flags: "si"
+          excludeDescription: "true"
+          excludeTitle: "false"
+          checkAllCommitMessages: "true"
+          accessToken: ${{ secrets.GITHUB_TOKEN }}
+          error: |
+            Fixup commits are not allowed in pull requests.
+
+            Found commit message starting with "fixup!" which must be squashed before merging.
+
+            To squash fixup commits, use:
+              git rebase -i --autosquash origin/${{ github.event.pull_request.base.ref }}
+
+            Or manually squash the fixup commits with their target commits.
+
+            After squashing, force push the updated branch:
+              git push --force-with-lease origin ${{ github.event.pull_request.head.ref }}
+
+      - name: Check for Cyrillic characters
+        uses: gsactions/commit-message-checker@v2
+        with:
+          pattern: "^[^А-Яа-яёЁ]*$"
+          flags: "si"
+          excludeDescription: "false"
+          excludeTitle: "false"
+          checkAllCommitMessages: "true"
+          accessToken: ${{ secrets.GITHUB_TOKEN }}
+          error: |
+            The commit message must contain only Latin characters.
+            Ensure there are no Cyrillic characters in the commit title or description.
+
+      - name: Check for conventional commit message
+        uses: gsactions/commit-message-checker@v2
+        with:
+          pattern: '^((feat|fix|build|chore|ci|docs|refactor|perf|style|test|revert)(\([\w\/-]+\))?!?: [^\n]+(\n\n(BREAKING CHANGE: [^\n]+|.+))?)$'
+          flags: "si"
+          excludeDescription: "true"
+          excludeTitle: "true"
+          checkAllCommitMessages: "true"
+          accessToken: ${{ secrets.GITHUB_TOKEN }}
+          error: |
+            The commit message does not follow the conventional commit format.
+
+            A conventional commit message should be in the format:
+              <type>[optional scope]: <description>
+
+              [optional body]
+
+              [optional BREAKING CHANGE footer]
+
+            Example:
+              feat(api): add new endpoint
+
+            Or for a breaking change:
+              feat!: send an email to the customer
+
+              BREAKING CHANGE: `extends` key in config file is now used for extending other config files
+
+            Allowed types are: feat, fix, build, chore, ci, docs, refactor, perf, style, test, revert.
+            A '!' can be added after the type/scope for breaking changes (e.g., feat!:, feat(api)!:).
+            Alternatively, a 'BREAKING CHANGE:' footer can be used in the commit body.
+
+            Please rebase and amend the commit messages.

hexrift-0.1.0/.github/workflows/check-schema-not-modified.yaml

@@ -0,0 +1,16 @@
+name: 🔒 Schema not manually modified
+
+on:
+  pull_request:
+    paths:
+      - "hexrift/components/schema/schema.json"
+
+jobs:
+  check:
+    name: 🚫 Block manual schema.json edits
+    runs-on: ubuntu-latest
+    steps:
+      - name: Fail — schema.json must not be edited manually
+        run: |
+          echo "::error file=hexrift/components/schema/schema.json::schema.json is auto-generated. Do not edit it manually — it is updated automatically on push to main."
+          exit 1

hexrift-0.1.0/.github/workflows/ci-code-quality.yaml

@@ -0,0 +1,32 @@
+name: 🔍 Check code quality
+
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  quality:
+    name: 🔍 Code Quality
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v7
+        with:
+          enable-cache: true
+          cache-dependency-glob: uv.lock
+
+      - run: uv sync --group dev
+
+      - name: Check formatting
+        run: uv run ruff format --check .
+
+      - name: Lint code
+        run: uv run ruff check .
+
+      - name: Type check
+        run: uv run ty check

hexrift-0.1.0/.github/workflows/create-tag.yaml

@@ -0,0 +1,95 @@
+name: 🚀 Tagged Release
+
+on:
+  push:
+    tags:
+      - "v*.*.*" # Semantic version tags: v1.2.3
+
+permissions:
+  contents: read
+  id-token: write
+  attestations: write
+
+jobs:
+  build:
+    name: 📦 Build distribution
+    runs-on: ubuntu-latest
+
+    steps:
+      - uses: actions/checkout@v6
+
+      - uses: astral-sh/setup-uv@v7
+
+      - run: uv build
+
+      - name: Upload distribution artifacts
+        uses: actions/upload-artifact@v5
+        with:
+          name: python-package-distributions
+          path: dist/
+
+  attest-artifacts:
+    name: 🔐 Generate artifact attestations
+    needs: build
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v8
+        with:
+          name: python-package-distributions
+          path: dist/
+
+      - name: Generate artifact attestations
+        uses: actions/attest-build-provenance@v4
+        with:
+          subject-path: dist/*
+
+  publish-pypi:
+    name: 📤 Publish to PyPI
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: pypi
+      url: https://pypi.org/project/netloom/
+    permissions:
+      id-token: write
+
+    steps:
+      - uses: astral-sh/setup-uv@v7
+
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v8
+        with:
+          name: python-package-distributions
+          path: dist/
+
+      - name: Publish to PyPI
+        run: uv publish --trusted-publishing always
+
+  create-release:
+    name: 📋 Create GitHub Release
+    needs: [publish-pypi, attest-artifacts]
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+
+    steps:
+      - uses: actions/checkout@v6
+
+      - name: Download distribution artifacts
+        uses: actions/download-artifact@v8
+        with:
+          name: python-package-distributions
+          path: dist/
+
+      - name: Create GitHub Release
+        env:
+          GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          TAG_NAME: ${{ github.ref_name }}
+        run: |
+          gh release create $TAG_NAME \
+            --title "🚀 Release $TAG_NAME" \
+            --verify-tag \
+            --generate-notes \
+            dist/*

hexrift-0.1.0/.github/workflows/labels.yaml

@@ -0,0 +1,25 @@
+name: 🏷️ Sync labels
+
+on:
+  push:
+    branches:
+      - main
+    paths:
+      - .github/labels.yaml
+  workflow_dispatch: {}
+
+jobs:
+  labels:
+    name: 🏷️ Sync labels
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+      issues: write
+
+    steps:
+      - uses: actions/checkout@v6
+      - uses: micnncim/action-label-syncer@v1.3.0
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          manifest: .github/labels.yaml