- How do I install Warriorfolio in a Laravel project?
- Install it with Composer using composer require mviniciusca/warriorfolio, then follow the repository README to publish any assets or configuration and run migrations. The v2.2.3 release notes reviewed here do not document a first-time install checklist, including required environment variables or mail and queue driver assumptions, so treat initial setup as a short discovery step. Check the package composer.json and README on the published tag before committing to a timeline.
- Which Laravel and PHP versions does Warriorfolio support?
- The supported Laravel and PHP ranges are not stated in the package overview or the v2.2.3 release notes, so verify them in composer.json on the tag you plan to use. The code is Laravel-native, with Eloquent-backed features, seeders and route middleware, so it should fit a standard Laravel monolith. Pin the version you test against and confirm constraints with composer why-not if you are on an older Laravel release.
- What features does the Warriorfolio admin dashboard provide?
- Warriorfolio ships an admin dashboard plus feature areas for projects, content and mail, and settings, so you can manage your portfolio without editing Blade files by hand. The overview also advertises pre-built components for showcasing work, clients and a resume, along with customizable templates. v2.2.3 added feature tests covering the Mail, Project and Settings areas plus routes and access control.
- Can I customize Warriorfolio's templates and layout?
- Yes, the package is described as offering customizable templates and pre-built components, letting you assemble portfolio pages quickly. In practice you will typically publish and override the Blade views and adjust configuration to match your branding. The reviewed notes do not list the exact publish tags or config keys, so check the README for the current asset and view publishing commands.
- Is Warriorfolio a Composer package or a full Laravel application?
- Warriorfolio is distributed as a Composer package, but the v2.2.3 release notes show app-level traits such as a HeroSectionSeeder, application routes and a committed local database.sqlite. That suggests a starter or demo codebase as much as a drop-in library, so decide early whether you are consuming it as a dependency or forking it as a template. Forking shifts maintenance onto your team, while depending on it makes a stable public API and upgrade path more important.
- How does Warriorfolio handle authentication and admin access control?
- Access control is handled at the route level with Laravel middleware, and v2.2.3 added feature tests specifically for routes and access control. You will need to wire the admin area into your existing auth guard and user model, and restrict registration to trusted users. Review the package routes and middleware groups after install to confirm who can reach the dashboard.
- What's new in Warriorfolio 2.2.3?
- v2.2.3 is a patch release focused on hygiene and test coverage rather than new features. It adds tests for the Mail, Project and Settings areas plus routes and access control, removes an obsolete SQLite test database and adjusts seeding, adds a .gitignore entry for local SQLite files, bumps the version string in HeroSectionSeeder and refreshes dependencies. No new endpoints, config keys, service providers or migrations are signalled, so it should be a no-op for existing 2.2.x consumers.
- Is Warriorfolio tested, and how do I run its test suite?
- The v2.2.3 release adds feature tests across Mail, Project, Settings, routes and access control, and uses SQLite as the test database. Run the suite with your usual PHPUnit or Pest command after installing dev dependencies. If your own CI fixtures referenced the package old SQLite test database or depended on the previous seeding behaviour, mirror the same adjustment in your harness.
- Is Warriorfolio safe to use in production?
- The 2.2.3 release itself is low risk, since it is a patch of tests, gitignore hygiene and dependency refreshes, but the notes only describe dependency updates as minor, so review transitive constraint changes with composer update and a locked diff. Confirm the supported PHP and Laravel ranges and verify the full suite is green on the tagged release before deploying. Also decide whether app-level pieces, such as the HeroSectionSeeder that hard-codes the version string, belong in your production build.
- How do I upgrade Warriorfolio from 2.2.2 to 2.2.3?
- No database migrations or breaking changes are signalled between 2.2.2 and 2.2.3, so upgrading is essentially pulling the tag and running composer update within your existing constraints. Re-run your application and package test suites afterwards, paying attention to any fixtures that used the removed SQLite test database. If you seeded content from the package, confirm the adjusted seeding behaviour still produces the data you expect.