mirror of
https://github.com/TronoSfera/backupy-agent.git
synced 2026-05-18 10:03:30 +03:00
Source ports from the TronoSfera/backupy-cloud monorepo:
- apps/agent/ — Go agent (WSS client, persistent queue, Docker
discovery, 5 DB drivers: PG/MySQL/Mongo/Redis/SQLite,
pre/post hooks, Prometheus metrics)
- apps/backupy-decrypt/ — standalone CLI for client-side decryption
- packages/proto/ — protobuf wire format (generated .pb.go committed
so the repo builds without protoc)
- docs/ — agent spec + wire-protocol contract
Apache-2.0 license. Image published to ghcr.io/tronosfera/backupy-agent
on every v* tag via .github/workflows/release.yml (multi-arch amd64+arm64).
34 lines
958 B
YAML
34 lines
958 B
YAML
# Backupy protobuf module — see docs/07-api-contract.md
|
|
#
|
|
# This module owns the canonical wire-format definitions used by:
|
|
# - apps/agent (Go)
|
|
# - apps/server (Go)
|
|
#
|
|
# Generated code lives under gen/ and is committed (small, deterministic,
|
|
# trivially regenerated via `make proto`).
|
|
|
|
version: v2
|
|
|
|
modules:
|
|
- path: .
|
|
|
|
lint:
|
|
use:
|
|
- STANDARD
|
|
except:
|
|
# Enum values in common.proto (e.g. POSTGRESQL, TCP, HTTP) are intentionally
|
|
# short and unprefixed because they read naturally in generated Go code as
|
|
# backupv1.POSTGRESQL etc. STANDARD's ENUM_VALUE_PREFIX would require
|
|
# DB_TYPE_POSTGRESQL, which is needlessly verbose.
|
|
- ENUM_VALUE_PREFIX
|
|
- ENUM_ZERO_VALUE_SUFFIX
|
|
# We use proto messages over WSS, not gRPC services, so service-related
|
|
# rules do not apply.
|
|
- RPC_REQUEST_STANDARD_NAME
|
|
- RPC_RESPONSE_STANDARD_NAME
|
|
- RPC_REQUEST_RESPONSE_UNIQUE
|
|
- SERVICE_SUFFIX
|
|
|
|
breaking:
|
|
use:
|
|
- FILE
|