Weave Code
Ai Surreal Db Message Store Laravel Package
symfony/ai-surreal-db-message-store
SurrealDB message store integration for Symfony AI Chat, letting you persist and retrieve conversation messages in SurrealDB via its HTTP integration.
SurrealDB Message Store provides a persistent message store integration for Symfony AI Chat. It lets your chat applications store and retrieve conversation messages in SurrealDB, a multi-model database, using its HTTP integration.
- Persistent chat history backed by SurrealDB
- HTTP-based integration with the SurrealDB API
- Drop-in message store for Symfony AI Chat
- Configurable through Symfony's service container
Frequently asked questions about Ai Surreal Db Message Store
- Is symfony/ai-surreal-db-message-store compatible with Laravel?
- No, it is not Laravel-compatible out of the box. The package is built for Symfony AI Chat and relies on Symfony components such as HttpClient, Serializer, and MessageStoreInterface. Laravel integration would require a custom bridge or a Laravel-native implementation.
- How do I install symfony/ai-surreal-db-message-store in a Laravel app?
- You can install it with Composer, but installation alone does not make it Laravel-ready. The package requires Symfony AI and does not provide a Laravel service provider or facade. You would need to wire its dependencies manually or build an adapter layer.
- What Laravel version can I use with this SurrealDB message store?
- There is no Laravel version compatibility range because the package targets Symfony AI Chat, not Laravel. Laravel version constraints do not apply directly to this package. Any Laravel use would depend on your own integration layer and supported Symfony AI versions.
- Can I use SurrealDB for chat history in Laravel without Symfony?
- Yes, SurrealDB can be a valid backend for Laravel chat history, but this package is not the right driver. You can use SurrealDB's HTTP integration through Laravel's Http facade or Guzzle. A Laravel-native message store would avoid Symfony lock-in and align with Laravel's container, events, and testing tools.
- What dependencies does symfony/ai-surreal-db-message-store require?
- It depends on Symfony AI and Symfony ecosystem components, including HttpClient, Serializer, and the MessageStoreInterface abstraction. It does not rely on Laravel's Http client, event system, or service container. Those differences are the main blockers for direct Laravel adoption.
- How does authentication work with SurrealDB in this package?
- The package communicates with SurrealDB through its HTTP integration and therefore follows SurrealDB's authentication model, including namespace, database, and token configuration. It does not provide Laravel middleware or Laravel-native auth integration. In Laravel, you would need to manage those credentials through config and a custom client wrapper.
- Is this package production-ready for Laravel applications?
- Not directly, because it is a Symfony AI Chat bridge rather than a Laravel package. Using it in Laravel introduces high integration risk around HTTP handling, exceptions, events, and dependency injection. A Symfony microservice or a custom Laravel implementation is usually safer for production.
- What are alternatives to this package for Laravel and SurrealDB?
- For Laravel, consider a custom SurrealDB message store built on Laravel's Http facade or Guzzle. Community SurrealDB PHP clients or Laravel-specific SurrealDB packages may reduce integration work if they are actively maintained. Native Laravel drivers for PostgreSQL or Redis are also alternatives when SurrealDB's features are not essential.
- How do I test this package in a Laravel test suite?
- The package is aligned with Symfony's testing approach, not Laravel's PHPUnit and HTTP fake tooling. Laravel tests would need custom mocking for Symfony HttpClient calls and manual container setup. Rewriting the integration tests around Laravel's testing helpers is usually necessary.
- Will this package receive Laravel-specific updates and support?
- No, it is maintained within the Symfony AI ecosystem and is not targeted at Laravel. Laravel-specific features, service providers, and compatibility fixes should not be expected. Teams needing Laravel support should fork, wrap, or build a separate Laravel-native package.
Weaver
How can I help you explore Laravel packages today?