- Is routmoute/routmoute-discord-bundle compatible with Laravel?
- The package is published as a Symfony bundle, so its native integration path is Symfony's dependency injection and bundle configuration. The blurb markets it as a Laravel/PHP package, but there is no mention of a Laravel service provider or facade. Laravel teams should plan to bind the services manually and verify composer.json constraints before adopting.
- How do I install and configure routmoute-discord-bundle?
- Install it with Composer using composer require routmoute/routmoute-discord-bundle, then register the bundle and supply Discord credentials through the package configuration and environment variables. You will need a Discord application registration, a bot token or webhook URL, and the guild and channel identifiers you intend to use. In Laravel you should expect to wire the services yourself rather than relying on auto-discovery.
- Does this package support Discord OAuth2 login?
- Yes. The package overview lists OAuth2 login support for Discord-based authentication, wrapped in reusable services. You configure your Discord client ID, client secret, and redirect URI, then route the callback through your application. The bundle handles the Discord side; you still own session and user provisioning logic.
- What Discord API endpoints can I call with the API client helpers?
- Release 1.1.0 adds a Discord API service that wraps REST endpoints, with helpers for common operations such as messages, channels, and webhooks. The overview describes API client helpers for common Discord endpoints rather than a complete SDK. Check the source for the exact endpoint coverage before designing around it.
- Is routmoute-discord-bundle REST-only or does it support Discord gateway websockets?
- The available context describes REST endpoints and does not mention gateway or websocket support, so treat it as REST-only until you verify the source. Gateway connectivity would require persistent workers, reconnect logic, and sharding, which is a different operational profile. If you need real-time events, confirm this explicitly before committing.
- How are Discord rate limits handled by this package?
- Discord enforces per-route buckets plus a global limit keyed to the bot token, so naive retries can turn 429 responses into a retry storm. The provided assessment does not confirm whether this package respects retry_after, applies jittered backoff, or tracks buckets. Inspect the HTTP client code and add your own bucket-aware backoff wrapper if the defaults are insufficient.
- Are bot tokens and webhook URLs kept out of logs and exception traces?
- The technical assessment flags credential leakage as a risk, particularly through logs, exception traces, and queued job payloads. Bot tokens and webhook URLs are bearer secrets, and a webhook URL is effectively an unauthenticated credential. Verify that the package redacts secrets by default, and avoid serializing them into jobs or exception context in your own code.
- Can I test Discord integration without hitting the real API?
- Yes. You can contract-test the integration with Laravel's HTTP fake facilities, asserting the requests your code sends without calling Discord. Add one sandbox smoke test against a private guild or a test webhook to cover the live path. Keep that smoke test out of the default CI suite so it does not depend on external credentials.
- What changed in version 1.1.0 and is the project actively maintained?
- Version 1.1.0 is described as an additive minor release that adds a Discord API service, but the release note is only one line, so the assessment is provisional. Diff the 1.0.x tag against 1.1.0 to confirm there is no bumped PHP or Laravel floor, no new transitive dependencies, no changed shared HTTP client options, and no edits to existing public APIs. The context does not establish release cadence or a security disclosure policy, so ask the maintainer before relying on it long term.
- What are the alternatives to routmoute-discord-bundle for Laravel Discord integration?
- For Laravel applications, framework-native options such as laravel-notification-channels/discord cover webhook notifications, while Discord bot workflows often use a dedicated bot library. This bundle is the better fit when you want Symfony-style DI and configuration and are comfortable wiring it into Laravel. Compare based on whether you need REST-only calls, OAuth2 login, or gateway connectivity.