# Tremvok > One GitHub Action for the whole deploy side: GitHub Pages, Cloudflare Workers, S3/CloudFront, Lambda, Terragrunt and Ansible, verified after the fact. Canonical documentation for Tremvok, served at https://docs.magmamoose.com/tremvok/. The full text of every page below is at `llms-full.txt`. Each link is the page's markdown. The page itself is the same address without the `index.md`, or with `.html` in place of `.md`. ## Docs - [Action reference](https://docs.magmamoose.com/tremvok/action-reference/index.md): Generated by scripts/gen_action_reference.py. Edit action.yml, not this page. For the task-shaped version, see Setup. - [Agent readiness](https://docs.magmamoose.com/tremvok/agent-readiness/index.md): A docs site built by either docs target is readable and usable by AI agents without any setup: the build writes what an agent looks for into the site it publishes. A few things live outside the site (DNS records, zone rules, an OAuth server), and those are the owner's to add. This page says which is which. The… - [API reference](https://docs.magmamoose.com/tremvok/api/index.md): Optional. Leave the action's api-url empty and nothing here is called. - [Architecture](https://docs.magmamoose.com/tremvok/architecture/index.md): Two surfaces, one repository, no shared imports. - [Azure: a Function or API Management?](https://docs.magmamoose.com/tremvok/azure-functions-or-api-management/index.md): Both Azure targets give a repository an HTTP endpoint it deploys into: azure-functions-zip publishes code to a Function App, azure-apim-policy publishes policies to an API Management API. They suit different jobs, and the job decides. - [Configuration reference](https://docs.magmamoose.com/tremvok/configuration/index.md): The action's inputs live in the action reference. This page covers the other two configuration surfaces: the API's environment variables and the Terraform module's input variables. - [Tremvok](https://docs.magmamoose.com/tremvok/index.md): One GitHub Action for the whole deploy side. It's the counterpart to Diatreme. - [Migrating to v2](https://docs.magmamoose.com/tremvok/migration/index.md): v1 is the docs-only action. v2 is one action covering multiple deployment targets, so the input surface had to grow a selector and the docs inputs had to move out of the way of it. - [Roadmap](https://docs.magmamoose.com/tremvok/roadmap/index.md): Tremvok's scope is deployment orchestration and notification: the deploy-side counterpart to Diatreme. One action covering several deployment targets, not a family of narrow ones. - [Setting Tremvok up](https://docs.magmamoose.com/tremvok/setup/index.md): Pick a target, add the job, grant the permissions that target needs. The action reference has every input and the exact permission block per target; this page is the task-shaped version. - [Troubleshooting](https://docs.magmamoose.com/tremvok/troubleshooting/index.md): Every entry here is an error the action or the API actually emits. The message is quoted as it appears in the log.