Weave Code
Beskedfordeler Symfony Laravel Package
itk-dev/beskedfordeler-symfony
A Symfony integration from itk-dev for Denmark's Beskedfordeler message distribution service, giving applications the plumbing needed to receive, route and handle messages delivered through the shared public-sector messaging infrastructure.
beskedfordeler-symfony
Frequently asked questions about Beskedfordeler Symfony
- Can I install itk-dev/beskedfordeler-symfony in a Laravel application?
- Composer may resolve it, but it is a Symfony bundle, not a Laravel package. It ships a Bundle subclass, a DependencyInjection extension compiled against Symfony's ContainerBuilder, and service definitions in Resources/config/services.yaml, with no Laravel ServiceProvider, no facade, and no publishable config. In a Laravel app it will either fail resolution, resolve but be inert, or force you to hand-build a container shim before it does anything. Treat it as not installable for a standard Laravel project.
- Does itk-dev/beskedfordeler-symfony support Laravel 10 or Laravel 11?
- No. There is no illuminate/* dependency in the manifest and no Laravel service provider, so Laravel 10 and 11 are not supported targets. The last release was 23 March 2023, well before those framework versions, and there are no compatibility fixes for PHP 8.3 or 8.4 either. Any Laravel support would have to be written and maintained by you.
- Why can't Laravel use a Symfony bundle directly?
- Laravel already pulls in many Symfony components transitively, such as http-foundation, console, routing, process, and finder, so the components themselves coexist fine. What does not coexist is the bootstrapping: Symfony bundles expect a compiled ContainerBuilder, a bundle extension class, and YAML service definitions, none of which Laravel's ServiceProvider and Illuminate container understand. Getting services out of the bundle means compiling a second container and re-exposing the resolved services as Laravel bindings. That is bespoke, undocumented glue code for a zero-star package.
- What is the best way to use Beskedfordeler in a Laravel app?
- Fork and port the code rather than trying to adapt the bundle. The Symfony-specific plumbing, including the bundle class, DI extension, services YAML, and likely the controller base, is throwaway, while the domain logic such as payload DTOs, the transport client, and message-type dispatch is usually a small fraction of the lines. Wrap that in a Laravel ServiceProvider with config/beskedfordeler.php, an Illuminate\Support\Facades\Http client, and a queued Job. A one to two day spike reading src/ will confirm which path applies to your case.
- Is there a maintained Laravel package for the Danish Beskedfordeler?
- Not one that this package points to. itk-dev/beskedfordeler-symfony has zero stars and zero dependents, so there is no downstream ecosystem to borrow patterns from. Because the Fælleskommunal Beskedfordeler is Danish public-sector infrastructure, most working integrations are private and never published. Plan on building your own Laravel wrapper or asking Kombit about current reference implementations.
- Does the package handle the transport or only define a handler contract?
- Verify this in src/ first, because the answer changes the effort estimate by an order of magnitude. The bundle may poll the Beskedfordeler API or receive webhooks itself, or it may only define a handler contract and expect an external message queue to feed it. If the transport is missing, you are implementing the client, retries, and queueing yourself on top of Laravel's HTTP client and queue system. Read the source before scoping any work.
- What authentication does Beskedfordeler require for integration?
- Access runs through the Fælleskommunal Beskedfordeler and typically involves an OCES3 organisational certificate, mTLS, or OAuth2 client credentials, plus a registration or agreement with Kombit. Check whether the package hardcodes endpoints and credentials or exposes them through configuration, because hardcoded values mean patching vendor code. You also need access to the official test environment before you can exercise the integration at all.
- Is itk-dev/beskedfordeler-symfony safe to run in production with citizen data?
- Treat it as unknown until you have audited it. These messages carry citizen personal data, so if the package logs payloads or exception contexts at debug level you have a GDPR problem on deployment day. Verify logging behaviour, retention, and any error handlers that dump message bodies before going live. There is no security release channel, so no one will notify you when an upstream fix lands.
- Is the package still maintained?
- The last release was 23 March 2023, making it roughly two and a half years stale. It is effectively single-maintainer, published by itk-dev, a Danish municipal IT consultancy, with no community around it, no dependents, and no bug-report corpus to mine. There are no fixes for PHP 8.3 or 8.4 and none for Symfony 7, and none should be expected. Your fork becomes the maintained version.
- Can I test a Beskedfordeler integration locally without production access?
- Not meaningfully. Exercising the code requires a Kombit registration, an organisational certificate or client credentials, and access to the official test environment, so you cannot smoke-test it from a laptop. That means integration defects surface late, often in a shared environment. Budget for a stub transport behind an interface so routing and message handling can be unit tested with Laravel's HTTP fake and queue fakes instead.
Weaver
How can I help you explore Laravel packages today?