Ares Next

Tracker P2P + busca de arquivos com hash. Backend Rust (axum) na Fase 1.

Deploy (Fase 1 — Coolify + Gitea)

• Repo: https://git.hokmatech.com/Hokma-tech/ares-next.git (branch main)
• App Coolify: ares-next / env production, domínio https://ares.hokmatech.com
• Build: server/Dockerfile multi-stage (musl), base_directory=/server, dockerfile_location=/Dockerfile
• Volume: /data → host /data/aresnext (banco em /data/aresnext.db via ARS_NEXT_DB)
• DNS: registro A ares → 13.140.174.24 no Cloudflare com proxy ON (HTTPS no edge + Origin CA no origin; SSL mode strict)
• API pública: https://ares.hokmatech.com/api/v1/{health,search,files,peers,stats} e WS wss://ares.hokmatech.com/api/v1/tracker/ws

Endpoints:

• GET /api/v1/health — status do serviço
• GET /api/v1/search?q=...&limit=...&sort=... — busca FTS5 com filtro e ordenação
• GET /api/v1/files/{file_id} — registro do arquivo
• POST /api/v1/announce — anúncio de arquivo (peer_id, name, description, type, extension, size_bytes, hash 64-hex, license)
• GET /api/v1/peers/{file_id} — pares on-line do arquivo
• GET /api/v1/stats — estatísticas globais
• WS /api/v1/tracker/ws — registrar peer (msg {"type":"register","peer_id","file_id"}); broadcast peer_online