Weave Code
Gitea Laravel Package
socialiteproviders/gitea
Socialite Providers Gitea adds Gitea OAuth2 login to Laravel's Socialite, so users can sign in with self-hosted or public Gitea accounts. Install via Composer, register the provider and listener, set your client ID, secret, and instance URL, then enable Gitea authentication in your app.
[READ ONLY] Subtree split of the SocialiteProviders/Gitea Provider (see SocialiteProviders/Providers)
Frequently asked questions about Gitea
- How do I install socialiteproviders/gitea in a Laravel app?
- Install the package with Composer by requiring socialiteproviders/gitea in your project. It is PSR-4 autoloaded, so you do not need to manually include provider files. After installation, register the SocialiteProviders listener and configure your Gitea OAuth credentials.
- How do I configure the Gitea Socialite provider?
- Add your Gitea OAuth client ID, client secret, and Gitea instance URL to your Laravel configuration. Register the Gitea driver through the SocialiteProviders manager so Socialite knows which provider class to use. Then create the matching OAuth application inside your Gitea instance with the correct callback URL.
- Does this package work with self-hosted Gitea instances?
- Yes, the package is designed for Gitea OAuth2 and works with any Gitea instance URL, including self-hosted installations. You configure the base URL of your Gitea instance along with the OAuth client ID and secret. The OAuth callback URL in Gitea must match the callback route in your Laravel app.
- What user profile data does the Gitea provider return?
- The provider returns Gitea user profile data such as username, email, and avatar. You access it through the usual Laravel Socialite user object after the OAuth callback completes. Additional fields depend on what Gitea exposes and how the provider maps the response.
- Which Laravel versions are supported by socialiteproviders/gitea?
- Supported Laravel and PHP versions are defined by the package Composer constraints and its Socialite dependency. Check the package composer.json or Packagist metadata before installing in an existing application. Keeping Laravel Socialite and the provider package aligned avoids dependency conflicts.
- How do I register the SocialiteProviders listener for Gitea?
- Register a listener for the SocialiteProviders SocialiteWasCalled event in your Laravel application. In that listener, extend Socialite with the gitea driver and the package provider class. The exact registration location depends on your Laravel version and whether you use event discovery.
- Can I use Gitea login alongside other Socialite providers?
- Yes, Gitea is added as another Socialite driver, so it can coexist with providers such as GitHub, Google, or GitLab. Register each provider through SocialiteProviders and give each one its own routes and callback URL. Users can then choose which authentication method to use.
- How do I test Gitea OAuth login locally?
- Create an OAuth application in your Gitea instance and set its redirect URI to your local Laravel callback URL. If Gitea cannot reach localhost directly, use a tunnel or a publicly reachable development URL. Clear Laravel config caches after changing client ID, secret, or instance URL settings.
- Is socialiteproviders/gitea suitable for production?
- It is a thin OAuth2 provider that plugs Gitea into Laravel Socialite, so production suitability depends on correct configuration and secure secret handling. Use HTTPS, store the client secret in environment variables, and restrict the callback URL in Gitea. Ensure your self-hosted Gitea instance is reachable by users and by the OAuth redirect flow.
- What are alternatives to socialiteproviders/gitea for Gitea login?
- You can write a custom Laravel Socialite driver for Gitea or use a generic OAuth2 client and map the Gitea API response yourself. This package is a focused option when you want Gitea authentication through the SocialiteProviders ecosystem with minimal custom code. Built-in Socialite providers do not include Gitea by default.
Weaver
How can I help you explore Laravel packages today?