- How do I install joelbutcher/socialstream in a Laravel application?
- Install it with Composer using composer require joelbutcher/socialstream, then publish and review the package configuration and any required migrations. Wire it into your existing Jetstream or Fortify authentication scaffolding and configure OAuth credentials and redirect URIs for each provider. Run your test suite and verify the full login, registration, and callback flow in staging before deploying.
- Does Socialstream support Laravel 12?
- Yes. Version 6.3.0 explicitly adds Laravel 12 support and includes a Composer dependency fix, so new Laravel 12 projects can adopt it without pinning to an older Laravel line. You should still confirm the package's PHP and Socialite constraints in composer.json before upgrading. If you are on Laravel 10 or 11, verify the compatible Socialstream release line rather than assuming v6.3.0 covers it.
- Which OAuth providers can I use with Socialstream?
- Socialstream integrates with Laravel Socialite and supports providers such as GitHub, Google, and Facebook. Additional providers depend on the Socialite provider packages and SDK versions your application installs. Check the provider-specific SDK compatibility and configure separate credentials and callback URLs for each provider you enable.
- Is Socialstream compatible with Jetstream and Fortify?
- Yes. Socialstream is designed to integrate with Jetstream and Fortify, letting users sign in and register with social providers and manage connected accounts from their profile. Validate the fit against your app's auth scaffolding and session model, especially if you use Breeze or custom authentication. Test the combined flows in staging after any Laravel or package upgrade.
- How do I upgrade Socialstream from 6.2.x to 6.3.0?
- Bump the Composer constraint to ^6.3.0, run composer update, and execute your test suite. There are no explicit breaking changes noted for this minor release, so existing v6.2.x consumers should generally be able to upgrade. Verify OAuth callbacks, account linking, and logout in staging before production rollout.
- Can users link and unlink multiple social accounts with Socialstream?
- Yes. Socialstream lets users manage connected social accounts from their profile, including linking and unlinking providers. Account-linking edge cases such as collisions with existing emails or previously connected providers should be tested explicitly. Also verify behavior when a provider token is expired or revoked.
- What should I check for redirect URI and state/session errors in Socialstream?
- Redirect URI mismatches are a common cause, so ensure each provider's callback URL exactly matches your application configuration in every environment. State and session mismatches can occur when sessions are not shared or callback endpoints fail across load-balanced instances. Confirm callback routing, session storage, and provider settings before diagnosing deeper OAuth issues.
- What are the main production risks of using Socialstream for social login?
- Key failure modes include provider outages, misconfigured redirect URIs, state or session mismatches, expired or revoked provider tokens, Composer dependency conflicts, and account-linking collisions. Social auth is request-bound and unlikely to be your primary scaling bottleneck, but callback endpoints must work across all instances. Keep a non-social login fallback so users can still access your application during provider incidents.
- How actively maintained is joelbutcher/socialstream?
- It is a community-supported open source package, and v6.3.0 is a minor release that improves Laravel 12 compatibility and fixes Composer dependencies. Keep it pinned and monitored with Dependabot or Renovate, and track Laravel, Socialite, and OAuth provider changes as the main maintenance drivers. Your team still owns provider credentials, redirect URI configuration, and incident response.
- How should I test Socialstream social authentication before deploying?
- Use provider sandbox credentials and staging callback URLs that match your production configuration. Regression-test login, registration, account linking and unlinking, callback errors, and logout, plus Laravel 12 compatibility if you are upgrading. Run these checks in lockstep with Laravel upgrades and deploy as a canary with monitoring.