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

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 fcb3ad2a01
2 changed files with 13 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
.goreleaser.yml
View File

@@ -1,8 +1,9 @@
# Publishes provider binaries to a Gitea release. # Publishes provider binaries to a Gitea release.
# #
# Gitea has no Terraform provider registry -- that protocol is not one of the # These archives are consumed through a filesystem mirror, because Gitea cannot
# ~20 package types it implements -- so these archives are consumed through a # serve the provider protocol. Its package registry list does include
# filesystem mirror instead. See "Installing" in the README. # "Terraform", but that one stores remote state for the `http` backend -- it is
# neither a module nor a provider registry. See "Installing" in the README.
# #
# The archive names follow HashiCorp's convention # The archive names follow HashiCorp's convention
# (terraform-provider-NAME_VERSION_OS_ARCH.zip) because a filesystem mirror # (terraform-provider-NAME_VERSION_OS_ARCH.zip) because a filesystem mirror

14
README.md
View File

@@ -57,11 +57,15 @@ resource "dokploy_domain" "api" {
## Installing ## Installing
This provider is distributed through This provider is distributed through
[Gitea releases](https://gitea.coolify.vojtkov.dev/usr_unknown/terraform-provider-dokploy/releases), [Gitea releases](https://gitea.coolify.vojtkov.dev/usr_unknown/terraform-provider-dokploy/releases)
not a Terraform registry — Gitea implements about twenty package registries, and installed through a **filesystem mirror**, which is Terraform's supported
and the Terraform provider protocol is not one of them. So installation goes way to use a provider that no registry serves.
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 ### From a release