Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Gitea backend for CMS #271

Open
jimafisk opened this issue Feb 17, 2023 · 2 comments
Open

Gitea backend for CMS #271

jimafisk opened this issue Feb 17, 2023 · 2 comments
Labels
cms Git-backed content editing enhancement New feature or request

Comments

@jimafisk
Copy link
Member

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
Copy link
Member Author

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 jimafisk added enhancement New feature or request cms Git-backed content editing labels Jun 1, 2023
@jimafisk
Copy link
Member Author

jimafisk commented Jun 2, 2023

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cms Git-backed content editing enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant