Administrator and Operator Guide

This guide covers deploying, configuring, and operating fogwall. It is written for the person responsible for running the proxy — setting up user accounts, configuring providers and rules, diagnosing problems, and keeping the service healthy.

For the YAML configuration reference, see Configuration Reference. For developers pushing through the proxy, see User Guide.

Contents

• Conceptual model: three independent layers — how access rules, permissions and approval fit together
• Developer onboarding — the Setup page — what a new developer sees on their first visit
• User accounts — provisioning, roles, emails and SCM identities
• Repo permissions — who may push, approve, self-certify or propose where
• Access rules — which repositories fogwall will proxy at all
• Approval mode — auto-approve versus human review
• Logging — log locations, debug profiles, and reading a failed push
• JGit filesystem requirements — home directory, /tmp, and gitleaks permissions
• Externalized configuration — mounting config into a container and overriding it
• Network requirements — outbound connections, corporate proxies, reverse proxies, sizing
• Production checklist — what to settle before the first real push
• SSH transport — exposing SSH, host keys, identity verification and agent forwarding
• SCM OAuth account linking — registering OAuth apps and operating strict identity mode
• SCM API — enabling the PR/MR path, its token model and authorization
• Common operational problems — symptoms an operator sees, and what causes them