Weave Code
Stash Api Bundle Laravel Package
medicorenl/stash-api-bundle
Laravel/PHP bundle that wraps the Stash caching library in a convenient API, letting you register cache pools, switch storage drivers, and manage keys with minimal configuration for fast, PSR-compliant caching.
Stash REST api integration in Symfony
Frequently asked questions about Stash Api Bundle
- Is medicorenl/stash-api-bundle compatible with Laravel?
- No, not natively. It is a Symfony bundle that registers through Symfony's Kernel, DependencyInjection Extension, and Configuration tree, which Laravel does not consume. Composer will autoload the classes, but the bundle's service wiring and config merging will be inert in a Laravel app. Laravel integration only works if the underlying Stash client classes are framework-agnostic and can be instantiated manually.
- How do I install medicorenl/stash-api-bundle in a Laravel application?
- You can run composer require medicorenl/stash-api-bundle, but do not expect Symfony bundle auto-registration to work. You would need to instantiate the Stash client classes yourself inside a Laravel service provider. Before doing that, confirm the client does not depend on Symfony's container, HttpClient, EventDispatcher, or Config components.
- Does this package support Bitbucket Server or Bitbucket Data Center?
- It targets Atlassian Stash, which Atlassian rebranded to Bitbucket Server and later consolidated into Bitbucket Data Center. The REST surface has been versioned and deprecated across that transition. You must confirm which API generation the client targets and which Atlassian product version your organisation actually runs before scoping any work.
- What PHP and Symfony versions does medicorenl/stash-api-bundle require?
- The README does not state this, so check composer.json directly. Legacy Symfony bundles frequently cap at PHP 7.x and Symfony 3 or 4, which can conflict with a modern Laravel 10 or 11 stack on PHP 8.2 and above. Use composer why-not or composer update dry runs against your lockfile to see whether the constraints resolve.
- Is medicorenl/stash-api-bundle actively maintained?
- There is no evidence of active maintenance. The package has zero stars, zero dependents, and no downstream adoption signals, so treat it as unmaintained until proven otherwise. That means no security patching path, no bug triage, and no compatibility updates as PHP, Symfony, and Atlassian versions move.
- Can I use the Stash API client without Symfony's dependency injection container?
- That depends entirely on how the code is structured. Best case, the HTTP client layer is a set of PSR-18-compatible classes that take an HTTP client and credentials via the constructor, so you can wire them manually in a Laravel service provider. Worst case, business logic lives inside bundle services resolved from the container or relies on Symfony HttpClient or EventDispatcher, which makes extraction expensive.
- What authentication methods does this Stash bundle support?
- The README does not document the auth model. You need to check the source for basic auth, personal access token, or OAuth support. Stash and Bitbucket Server instances may now enforce stricter authentication than when this bundle was written, so verify against your own instance before committing.
- Is this package a better choice than writing my own Laravel Stash client?
- Usually no. Writing a small Laravel-native client with a handful of endpoints behind an interface, using Http::withToken for transport, is often cheaper than adapting a Symfony bundle. Only consume the package directly if its client layer is clean, framework-agnostic, and extractable without Symfony bootstrapping.
- Which Stash REST endpoints does medicorenl/stash-api-bundle cover?
- The README excerpt does not say, so inspect the source. You need to confirm coverage for the endpoints you actually use, such as repositories, pull requests, branches, commits, and webhooks. Many older Stash clients cover only a subset, which may force you to write missing calls anyway.
- What license does medicorenl/stash-api-bundle use, and can I fork it?
- Check the repository and composer.json for the declared license before assuming you can reuse or redistribute it. If the client classes are clean but the bundle glue is not, a common middle path is to fork, copy out the client classes, drop the bundle metadata, and pin your own fork. You should also contact MedicoreNL to ask about maintenance status, a fork, or a transfer.
Weaver
How can I help you explore Laravel packages today?