- How do I install the pwinty/php-pwinty package in a Laravel project?
- Add the package via Composer using `composer require pwinty/php-pwinty:dev-master`. Since it’s not published officially, ensure your `composer.json` explicitly targets the `dev-master` branch. The package requires no Laravel-specific setup, but you’ll need to manually initialize the client with your API key and merchant ID.
- Does this package support Laravel’s service container or facades?
- No, the package is vanilla PHP and doesn’t integrate natively with Laravel’s service container or facades. You’ll need to wrap the client in a Laravel service class (e.g., `app/Services/PwintyService.php`) and bind it in a service provider for dependency injection.
- What Laravel versions does pwinty/php-pwinty support?
- The package doesn’t enforce Laravel-specific dependencies, so it *technically* works with any Laravel version. However, it may rely on older PHP features (e.g., Guzzle <7.x) or lack PSR standards compliance. Test thoroughly with your Laravel version (e.g., 8.1+) and PHP version (e.g., 8.0+).
- Can I use this package in production without issues?
- The package is **archived**, meaning no active maintenance or updates. Use it cautiously in production, especially if Pwinty’s API changes. Plan for potential breaking changes or fork the repo to apply fixes. Monitor Pwinty’s API documentation for updates that might break compatibility.
- How do I handle API authentication (keys, tokens) securely?
- Store your Pwinty API key and merchant ID in Laravel’s `.env` file (e.g., `PWINTY_API_KEY`, `PWINTY_MERCHANT_ID`). Initialize the client in a service class and inject the config dynamically. Avoid hardcoding credentials in your codebase or version control.
- Are there alternatives to pwinty/php-pwinty for Laravel?
- Yes. Check Pwinty’s official documentation for an updated SDK or API wrapper. Alternatively, use Guzzle directly to call Pwinty’s API endpoints, which gives you full control but requires more boilerplate. Other print-on-demand services (e.g., Printful, Printify) may offer more maintained Laravel-compatible packages.
- Does this package support webhooks or real-time order updates?
- The current wrapper does **not** include webhook functionality. You’ll need to extend the package manually or poll Pwinty’s API for order status updates. If webhooks are critical, consider using Guzzle directly or forking the repo to add this feature.
- How do I test this package in my Laravel app?
- Write unit/integration tests using Laravel’s testing helpers (e.g., `Http::fake()` for mocking API responses). Test critical flows like order creation, photo uploads, and status updates. Since the package lacks built-in testing tools, mock Pwinty’s API responses to avoid external dependencies.
- Can I extend the package to add missing Pwinty API features?
- Yes, the package is open-source. You can extend it by creating a trait or subclass (e.g., `app/Extensions/PwintyClientExtension.php`) to add unsupported endpoints like bulk operations or custom webhooks. Document your changes and consider contributing back to the community.
- What’s the fallback if the package breaks or becomes unsupported?
- Fallback to direct API calls using Guzzle or Laravel’s HTTP client. The package’s source code is available, so you can replicate its functionality manually. Start by inspecting the wrapper’s implementation (e.g., how it handles requests/responses) to replicate critical features.