Weave Code
Makerlog Laravel Package
socialiteproviders/makerlog
Socialite provider for MakerLog that adds MakerLog OAuth login to Laravel applications. Install via Composer, configure credentials, and authenticate users through Laravel Socialite with a standard provider flow.
A Collection of Providers for Laravel Socialite
Frequently asked questions about Makerlog
- How do I install the MakerLog Socialite provider in Laravel?
- Install the provider with Composer by running composer require socialiteproviders/makerlog in your Laravel project. Then register the SocialiteProviders manager service provider and the MakerLog SocialiteWasCalled listener using the class names documented by SocialiteProviders. After that, clear your config cache and confirm the provider is available to Laravel Socialite.
- How do I configure MakerLog OAuth credentials in Laravel?
- Add a makerlog entry to config/services.php with client_id, client_secret, and redirect values sourced from environment variables. Create the OAuth application in MakerLog and set its redirect URI to match your Laravel callback route exactly. Cache the config after setting MAKERLOG_CLIENT_ID, MAKERLOG_CLIENT_SECRET, and MAKERLOG_REDIRECT_URI in your .env file.
- Which Laravel versions does socialiteproviders/makerlog support?
- The provided release note does not publish a Laravel version matrix, so you must inspect the composer.json illuminate/support constraint to see which Laravel majors are allowed. PHP 8 support was added in 4.1.0, which is required for Laravel 9 and later. Test the package against your exact Laravel and PHP versions before committing to it.
- Does this package support PHP 8?
- Version 4.1.0 added PHP 8 support according to the changelog, but the note does not specify which PHP 8 minors are covered. Check the package's CI matrix and composer.json php constraint for 8.1, 8.2, and 8.3 coverage. PHP 8.0 is end-of-life, so prefer a release that is tested on currently supported PHP versions.
- How do I authenticate users with MakerLog in Laravel Socialite?
- Use Socialite::driver('makerlog')->redirect() to send the user to MakerLog, then handle the callback with Socialite::driver('makerlog')->user(). Read the returned Socialite user's id, nickname, email, and avatar, then find or create a matching local user record. Store any MakerLog tokens you need and protect the callback route with your normal session and CSRF safeguards.
- Do I need to publish a config file for the MakerLog provider?
- Most SocialiteProviders packages do not ship a publishable config file; credentials are normally placed in config/services.php and environment variables. If this package includes a config file, publish it with php artisan vendor:publish and select the MakerLog provider tag. Read the package README to confirm whether publishing is required.
- How do I test MakerLog OAuth login in my Laravel app?
- Mock the Socialite driver in your feature tests so you do not call MakerLog during the test run. Use Laravel's HTTP fake or a Socialite mock to return a known user payload from the callback flow. Also test the failure path where MakerLog returns an error or a user without an email address.
- Is socialiteproviders/makerlog maintained and safe for production?
- Treat production adoption as a due-diligence item because the available evidence is a single-line 4.1.0 changelog with no linked pull requests or migration notes. Check recent commits, issue response times, CI coverage for PHP 8 minors, and the declared illuminate/* bounds. Pin the exact version you audit and monitor the repository for maintenance signals before relying on it.
- What are alternatives to using this MakerLog Socialite provider?
- If MakerLog is not a built-in Laravel Socialite provider, alternatives are writing a custom Socialite driver, using a general OAuth client package, or implementing the MakerLog OAuth flow manually. A custom driver keeps the Socialite interface and may be preferable if you need full control over scopes and user mapping. Evaluate whether the MakerLog API and OAuth endpoints are stable enough for your use case.
- What should I check before upgrading to version 4.1.0?
- Before upgrading to 4.1.0, read the release diff and composer.json changes to confirm whether the release is constraint-only or includes functional changes. Run your application test suite on every PHP and Laravel version you deploy, paying attention to dynamic properties, strict types, and null handling. Require 4.1.0 explicitly in composer.json and avoid floating constraints until you have verified compatibility.
Weaver
How can I help you explore Laravel packages today?