Weave Code
Sst Laravel Laravel Package
kirschbaum-development/sst-laravel
Integrates Laravel with SST (Serverless Stack), offering configuration and deployment helpers to run Laravel applications on AWS Lambda and related serverless infrastructure. Simplifies wiring Laravel to SST-managed resources.
Deploy robust, auto-scalable Laravel applications to AWS Fargate using SST and Docker
Frequently asked questions about Sst Laravel
- How do I install kirschbaum-development/sst-laravel in a Laravel app?
- Install it with Composer using composer require kirschbaum-development/sst-laravel. The package provides Laravel service provider and configuration publishing plus SST construct helpers. You still need an existing SST application and an AWS account to deploy against.
- Does sst-laravel deploy Laravel to AWS Lambda or AWS Fargate?
- The package overview emphasizes deploying Laravel to AWS Fargate using SST and Docker, while related descriptions also mention AWS Lambda and serverless infrastructure. In practice, the target is determined by your SST configuration and the constructs you use. Confirm the supported target for your SST version in the package documentation before committing.
- Which Laravel, PHP, and SST versions does sst-laravel support?
- The technical assessment suggests it is best suited to Laravel 10 or 11 on PHP 8.1+ with SST v2 or v3. Official support ranges are not explicitly stated in the provided context, so verify the composer.json constraints and README. Because the package is pre-1.0, pin both the package and SST versions in production.
- How are environment variables and secrets handled at runtime versus build time?
- Release 0.7.4 improves container image environment handling to avoid baking environment variables into built images and fixes unset environment file outputs being emitted as undefined. Runtime values should be injected through SST-managed resources rather than embedded at build time. Validate this behavior explicitly in staging for your own SST configuration.
- Does sst-laravel support queues, scheduled tasks, storage, and Laravel Octane?
- The provided context does not confirm first-class support for queues, scheduled tasks, storage, or Laravel Octane. These capabilities depend on how you configure the underlying AWS and SST resources alongside your Laravel application. Treat Octane and Bref-style configuration as items to verify against your target runtime.
- Is sst-laravel production-ready at version 0.7.x?
- It is pre-1.0 and the technical assessment rates risk as moderate, with possible API and convention changes. The 0.7.4 fixes are positive but also show environment handling is still maturing. A sensible path is to validate in staging or a low-risk production service before broader adoption.
- How does sst-laravel compare with Laravel Vapor?
- Laravel Vapor is a managed Laravel serverless platform, while sst-laravel wires Laravel into SST's AWS infrastructure-as-code model. This package is aimed at teams that want AWS-native deployments without adopting Vapor. It is a poor fit if you need cloud portability or already standardize on Vapor, Kubernetes, or traditional containers.
- Can I use sst-laravel without an existing SST app or AWS account?
- No, integration requires an existing SST application and an AWS account. The package supplies Laravel-side configuration and SST construct helpers rather than a standalone deployment platform. Plan for AWS credentials, SST CLI setup, and CI/CD wiring as part of adoption.
- How should I test and validate an sst-laravel deployment before production?
- Prototype in a sandbox AWS account with a minimal Laravel app and verify environment and secret injection. Confirm that environment variables are not present in built container images and that unset environment outputs are omitted rather than emitted as undefined. Then move a staging service and a low-risk production service, with rollback and observability in place.
- How is sst-laravel maintained and what is the upgrade policy before 1.0?
- It is maintained by Kirschbaum Development and appears active, with 0.7.4 following 0.7.3 with targeted fixes. Because it is pre-1.0, periodic breaking changes are possible and no commercial SLA is indicated. Pin package and SST versions, review each release, and budget for dependency review and community-based support.
Weaver
How can I help you explore Laravel packages today?