Gitea backend for CMS

[jimafisk]

The people have spoken and they want Gitea backend support for the CMS: https://twitter.com/plentico/status/1615857323292987397

Blocker: Can't commit multiple files to a generic endpoint using the API: go-gitea/gitea#14619

Per these API Docs there are only the 2 following methods for manipulating repo files:

• PUT /repos​/{owner}​/{repo}​/contents​/{filepath} Update a file in a repository (link)
• POST ​/repos​/{owner}​/{repo}​/contents​/{filepath} Create a file in a repository (link)

[jimafisk]

We've also been having trouble getting PKCE to work clientside: https://discourse.gitea.io/t/oauth-pkce-example/6573

Sounds like you can't omit the client_secret in Gitea currently: go-gitea/gitea#17107

[jimafisk]

There's been progress on both the API endpoint and PKCE client secret: decaporg/decap-cms#1109 (comment) 🎉

• Multi-file API endpoint (API endpoint for changing/creating/deleting multiple files go-gitea/gitea#24887) - Merged ✔️
• PKCE optional client secret (Allow for PKCE flow without client secret + add docs go-gitea/gitea#25033) - Open 👀

[jimafisk]

In testing this, I was getting the following error after being redirected back to my website:

Only refresh_token or authorization_code grant type is supported

I forgot that you need to explicitly set the Content-Type when making your POST/fetch to request the access token (https://forum.gitea.com/t/oauth-pkce-example/6573):

headers: {
    "Content-Type": "application/x-www-form-urlencoded"
}

[jimafisk]

Gitea support should be available in v0.7.16 🎉

Just note we added a new provider key to the cms section in plenti.json:

"cms": {
	"provider": "gitea",
	"repo": "https://your-git-host.com/your-org/your-repo",
	"redirect_url": "https://your-static-site.com",
	"app_id": "your-oauth-id-from-gitea",
	"branch": "master"
}

The provider key is helpful since you can self-host Gitea and GitLab, which would make the repo live at a different URL than the officially supported ones (gitlab.com and gitea.com) which wouldn't necessarily communicate which platform you're on. If you omit this key, it defaults back to GitLab to ensure backwards compatibility with older version of Plenti.

Note that since the APIs have not diverged too much at this point, this release also supports the Gitea fork Forgejo and you can use that as a provider name if you prefer.