usr_unknown/terraform-provider-dokploy
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 2 Wiki Activity

Clarify which Terraform registry Gitea actually has
Some checks failed
build / build (push) Successful in 15m46s
Details
release / release (push) Failing after 26m57s
Details

Browse Source 
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.
This commit is contained in:
Max Vojtkov
2026-08-09 12:49:11 +03:00
parent abe4444d2b
commit c6f1942950
2 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

14
README.md
View File

@@ -57,11 +57,15 @@ resource "dokploy_domain" "api" {
## Installing
This provider is distributed through
[Gitea releases](https://gitea.coolify.vojtkov.dev/usr_unknown/terraform-provider-dokploy/releases),
not a Terraform registry — Gitea implements about twenty package registries,
and the Terraform provider protocol is not one of them. So installation goes
through a **filesystem mirror**, which is Terraform's supported way to use a
provider that no registry serves.
[Gitea releases](https://gitea.coolify.vojtkov.dev/usr_unknown/terraform-provider-dokploy/releases)
and installed through a **filesystem mirror**, which is Terraform's supported
way to use a provider that no registry serves.
Gitea *does* list "Terraform" among its package registries, which is
misleading here: that one stores [remote
state](https://docs.gitea.com/usage/packages/terraform) for the `http` backend.
It is not a module registry and not a provider registry, and there is no Gitea
endpoint that can serve the provider protocol `terraform init` speaks.
### From a release