Weave Code
Placid Laravel Laravel Package
placidapp/placid-laravel
Laravel integration for the Placid creative automation API, making it easy to generate images and videos from templates, manage collections, and automate dynamic creative assets in PHP apps via a clean facade and config.
✨ Automatic image creation from templates
Frequently asked questions about Placid Laravel
- How do I install placidapp/placid-laravel?
- Install it with Composer using composer require placidapp/placid-laravel. Then publish the package config and set PLACID_API_TOKEN plus any template identifiers in your .env file. The package provides a service provider and facade, so you can call it after configuration. A working proof of concept is typically achievable in under a day.
- Which Laravel and PHP versions does placid-laravel support?
- The package has not had a release since July 2022, so its supported Laravel and PHP matrix is unclear and likely predates Laravel 10 and 11. You should run a smoke test on your target versions, such as PHP 8.1 through 8.3 with Laravel 9 through 11, before committing. Expect to pin an older framework version or fork the wrapper if compatibility issues appear.
- Does placidapp/placid-laravel support the current Placid API?
- It is unknown whether the wrapper targets Placid API v1 or v2, and its endpoint and payload shapes may be outdated. Because the last release was in 2022, the package may call deprecated endpoints or assume older authentication details. Verify the actual HTTP calls against Placid's current API documentation before relying on it. Any mismatch can fail silently at runtime rather than during installation.
- How do I configure Placid templates in Laravel?
- The package ships with a config file that you publish into your Laravel config directory. You typically set your Placid API token and template identifiers through environment variables referenced in that config. Rendering correctness depends on templates managed in Placid's dashboard, which live outside version control, so treat template IDs as external configuration.
- Can I generate videos with placid-laravel or only images?
- The package is described as generating images and videos from Placid templates, although the core examples focus on image creation. Video rendering still depends on Placid's API capabilities and your template setup in the dashboard. Confirm the current API supports the video features you need, since the wrapper predates recent API changes.
- Is placidapp/placid-laravel still maintained?
- No, the package is effectively unmaintained: the last release was July 2022, it has around 58 stars, and a composite score of 0.44. There is single-maintainer risk and no visible security or compatibility patching. You should assume you may need to fork or replace it for long-term production use.
- How do I test Placid image generation in Laravel without calling the API?
- Because the package makes external HTTP calls, you should not hit Placid in unit tests. Wrap the Placid facade behind your own interface and fake that implementation in tests. If you call Placid directly through Laravel's HTTP client, use Http::fake to avoid real network requests. This keeps tests fast and avoids per-render costs.
- What are alternatives to placidapp/placid-laravel for dynamic images in Laravel?
- The simplest alternative is to call Placid's REST API directly with Laravel's Http facade in roughly 50 lines of code, eliminating the package dependency. You could also evaluate other image-generation services or local rendering libraries depending on your need for templates, video, and hosted rendering. If imagery is peripheral, a direct HTTP integration is often lower risk than an unmaintained wrapper.
- Is placid-laravel safe for production use?
- It can be used in production, but treat it as a thin, unmaintained SDK at the edge of your application. The main risks are API drift, unknown Laravel and PHP compatibility, per-render cost, latency, and availability of Placid's external service. Decouple it behind an internal ImageRenderer interface and keep a direct HTTP implementation so you can swap it without touching call sites.
- How should I handle Placid API errors and latency in Laravel?
- Every render is an external network call with per-unit cost and variable latency, so use timeouts, retries with backoff, and queued jobs for non-critical assets. Catch exceptions at your integration boundary and return a clear failure or placeholder rather than letting the Placid facade leak into controllers. Log request context, but avoid sending unnecessary customer PII to the third-party renderer.
Weaver
How can I help you explore Laravel packages today?