setup-go caches by default. act_runner's built-in cache server binds to
an address job containers cannot route to, so every restore and save
blocks until it times out:
Failed to restore: getCacheEntry failed: connect ETIMEDOUT 10.0.2.12:40789
Failed to save: reserveCache failed: connect ETIMEDOUT 10.0.2.12:40789
That was 634s of a 946s build. Disable caching until the runner's
cache.host points somewhere reachable, then turn it back on.
Gitea lists "Terraform" among its package registries, which reads as if
the provider could be published there. It stores remote state for the
http backend -- not modules, not providers.
Gitea implements no Terraform provider registry, so distribution goes
through release archives plus a filesystem mirror. GoReleaser targets
the Gitea release API; the archive names follow HashiCorp's convention
because that is the only shape a filesystem mirror recognises.
No GPG signing: signatures are a registry-protocol requirement and a
filesystem mirror never checks them.
Cross-repo links point at Gitea; Go module paths deliberately do not.
Plugin-framework provider covering projects, environments, applications,
Compose stacks, managed databases, domains, mounts, ports, redirects,
basic auth, registries, SSH keys, certificates and backup destinations,
over Dokploy's tRPC-over-REST API.
The shim package exposes the provider to other Go modules, which is how
pulumi-dokploy bridges it.
