New OAuth provider not appearing in Console during development (Hugging Face)
- 0
- 2
- Self Hosted
- Web
Hi team!
I'm contributing to Appwrite and currently working on adding Hugging Face as a new OAuth provider.
Here's what I've done so far:
- Implemented the HuggingFace provider class.
- Added it to the providers config.
- PHPUnit tests are passing.
- Rebuilt Appwrite using docker compose build and docker compose up -d.
The issue is that the new provider doesn't appear in the Console.
I verified that my config changes are being picked up—for example, if I comment out an existing provider like Amazon, it disappears from the Console. So it seems my changes are loading, but Hugging Face still isn't listed.
I also found the contributor documentation a bit confusing in a few places. For example, it mentions uploading a provider icon to an image/users directory, but that directory doesn't exist in the current repository, so I'm not sure if the docs are outdated or if I'm looking in the wrong place.
Is there another place where a new OAuth provider needs to be registered for it to appear in the Console (frontend, API, generated files, etc.), or am I missing a build step?
Any pointers would be greatly appreciated. Thanks!
probably because the console is also holding the list of possible oauth : https://github.com/appwrite/console/blob/main/src/lib/stores/oauth-providers.ts
Recommended threads
- `project_id_missing` in Cloud Function w...
I've got a cloud function written in `Dart-3.12` that I'm trying to create a file in a file bucket. I'm using the latest `dart_appwrite` sdk (`26.1.0`) and App...
- Can Appwrite logs be output without bein...
Hi, I'm trying to use the Better Stack Collector to forward my Appwrite logs to Better Stack. The issue is that Appwrite seems to format the logs for terminal ...
- Static site not being served
Hey everyone, I’m having an issue deploying a Vue/Vite app through self hosted Appwrite Sites and could use some help. Setup: * Appwrite is self-hosted with T...