- How do I install bjuppa/laravel-blog in a Laravel app?
- Install with composer require bjuppa/laravel-blog:^1.11, then publish the package config, migrations, and views using the documented vendor:publish tags. Review the published migrations for table-name collisions, run php artisan migrate, and configure the blog image disk. Finally, review package routes and apply your app's admin auth middleware before exposing the blog in production.
- Which Laravel and PHP versions does bjuppa/laravel-blog support?
- v1.11.2 adds Laravel 13 support, and the package is intended for Laravel 10-13 applications on PHP 8.1+, but you should verify the exact constraints in composer.json and CI for the release you install. The model-cast tests added in v1.11.2 are a positive signal for Eloquent integration, but they do not replace application-level integration tests. Validate against your exact Laravel and PHP patch versions before upgrading.
- How do I configure image storage for bjuppa/laravel-blog?
- The package stores blog images through Laravel filesystem disks, so you configure a disk and related paths rather than hard-coding local storage. For a public local disk, run php artisan storage:link and verify image URLs render correctly. For object storage, point the package at an S3-compatible disk and test uploads, URLs, and deletions. Because image references are tied to the configured disk, changing disks or paths later needs a migration plan.
- How do I secure the bjuppa/laravel-blog admin routes?
- The package provides route and controller wiring for blog administration, but access control is your responsibility. Put the admin routes behind your existing auth and authorization middleware, and verify there are no unauthenticated endpoints or route collisions. Review admin route names and prefixes in the published configuration and routes before production. Also review HTML content rendering and image upload permissions as part of the security review.
- Can I customize the Blade views and routes in bjuppa/laravel-blog?
- Publish the package views and edit the copies in your application rather than forking the package. Route customization depends on how the package registers routes, so review the service provider and published config, then override or wrap routes in your app where supported. Treat published views, routes, and migrations as application-owned surface area, and track changes so future package upgrades remain manageable.
- Does bjuppa/laravel-blog support S3 or object storage for blog images?
- The package uses Laravel filesystem disks for image handling, which means S3-compatible object storage can be configured like any other Laravel disk. However, the package is described as better suited to server-rendered apps with local or object-storage image handling, so test upload, URL, deletion, and CDN behavior rather than assuming clean S3 support. If you rely on S3, confirm the image path and disk configuration in staging before production.
- Is there an API or headless mode in bjuppa/laravel-blog?
- No, bjuppa/laravel-blog is opinionated around Laravel routing, controllers, and Blade rendering; the context does not describe an API or headless mode. For SPA or mobile clients, plan to build custom controllers and API resources around the Eloquent models instead of relying on package-provided routes. If headless content delivery is a core requirement, this package is a weaker fit than a dedicated content service.
- How does bjuppa/laravel-blog handle HTML or rich-text sanitization?
- The package context does not document where HTML or rich-text sanitization happens, so treat it as an application responsibility. Sanitize untrusted HTML before rendering, restrict blog authoring to trusted admin users, and review the published Blade views for raw output. Add tests for stored content and rendering paths, especially if you accept HTML from less-trusted contributors.
- How do I migrate existing blog content into bjuppa/laravel-blog?
- Install and migrate the package schema first, then map your existing posts, categories, tags, and authors into BlogEntry, BlogEntryContent, BlogAuthor, and related models. Images need special handling because BlogImage references are tied to the configured storage disk, so copy files to the target disk and update references consistently. Run the import in a non-production branch, validate URLs and rendered content in staging, and keep a rollback plan.
- What are the maintenance and upgrade risks of bjuppa/laravel-blog?
- bjuppa/laravel-blog is a community package with a small maintainer base and no commercial SLA or LTS commitment, so upgrade risk depends on timely Laravel major-version releases. v1.11.2 reduces the immediate Laravel 13 blocker, but published views, routes, and migrations become your application's responsibility and can complicate future upgrades. Pin a known version, test upgrades in staging, and review dependencies for conflicts and advisories.