- Is salla/laravel-starter-kit a Composer package I can require?
- No. It is a template repository you clone or fork, not a library you install with composer require. Once you fork it, the code becomes your application, so there is no vendor upgrade path or patch stream. That makes it a strong fit for greenfielding a new Salla app and a weak fit for bolting onto an existing Laravel platform.
- Which Laravel and PHP versions does the Salla starter kit support?
- Check the composer.json in the repository before committing, since that file is the source of truth for the pinned Laravel and PHP constraints. The last release was May 2024, so expect Laravel 10/11-era conventions rather than the newest framework version. Confirm those constraints sit inside your supported matrix, because a forked template's framework upgrade becomes your manual work.
- How do I install the Salla Laravel starter kit and run it locally?
- Clone or fork the repository, run composer install, copy the environment file, generate an app key, and run migrations against a local MySQL or Postgres database. Then point the app at a Salla dev store and complete an install plus webhook round-trip to prove the flows work. The kit is scaffolding, so expect to adjust configuration and secrets handling for your environment rather than following a one-click installer.
- Does it handle Salla OAuth, token refresh, and uninstall events?
- The kit is expected to include an OAuth handshake for Salla Custom Mode plus token persistence and refresh, but treat those as a reference implementation to review rather than a hardened component. Check specifically how tokens are encrypted at rest, whether refresh is queued or synchronous, and whether uninstall or app-removal deletes tokens and stops outbound calls. Token lifecycle is the classic silent-failure surface in marketplace apps, so write tests around refresh, revocation, and uninstall before going live.
- Does the starter kit verify Salla webhook signatures and deduplicate events?
- Verify this in the code before relying on it, because signature verification, replay protection, and idempotency are frequently minimal or absent in starter kits. Duplicate order or refund webhooks are a business-critical failure, so you want queued ingestion plus a dedupe key persisted per event. If the kit does not implement it, add signature validation and idempotency before your first production merchant.
- Does the Salla starter kit use Easy Mode or Custom Mode?
- The available evaluation notes point to an OAuth handshake for Salla Custom Mode, but you should confirm in the repository whether Easy Mode, Custom Mode, or both are supported. Which one you need depends on how much of the merchant UI you want Salla to host versus building yourself. Read the routes and controllers to see which flow the scaffold actually wires up.
- Can I use it for multi-store tenancy or multiple merchants per install?
- The scaffold is aimed at a single-purpose Salla app, so multi-store tenancy is likely something you build rather than inherit. If you need per-store isolation, verify how the store or merchant model relates to tokens and whether every API call is scoped to the right store. This is one of the areas where scaffold defaults become something you argue with instead of leverage.
- Is the Salla Laravel starter kit production-ready?
- Treat it as a demo-quality reference implementation, not a production-hardened base. Scaffold defaults around secrets handling, queue configuration, and error paths usually need work, and you should assume you own test coverage and CI. Budget time to harden OAuth refresh, webhook idempotency, and uninstall handling before your first real merchant.
- How do I upgrade a forked Salla starter kit when Laravel releases a new version?
- Manually. Because the kit is a fork rather than a dependency, you inherit every line and every framework upgrade yourself, with no patch stream from Salla. Track the upstream repository for changes you want to cherry-pick, and plan a recurring maintenance line item for framework and dependency upgrades. If you need an upgrade path, build your own app on top of the patterns rather than staying on the template.
- What are the alternatives to the Salla Laravel starter kit?
- You can build from scratch against Salla's API documentation, cherry-pick files from the kit into an existing Laravel app, or translate the patterns into another stack entirely. For PHP and Laravel teams, forking the kit is usually the fastest path to a working install flow against a dev store. For Node, Python, or Go teams, porting is cheaper from scratch than translating the scaffold.