Official Laravel boilerplate is minimalistic by design, empowering developers with flexibility while leaving many foundational decisions up to them.
This boilerplate fills that gap, providing pre-configured, best-practice-driven strong foundation. That means you start fast and build right from day one.
- βοΈ php 8.4
- βοΈ Laravel 12
- βοΈ Official Laravel boilerplate
- βοΈ Essential packages configured for a seamless local development experience
- βοΈ Configured
docker-compose.yml - βοΈ Xdebug configured in
devandciimage - βοΈ Useful and handy composer commands for streamlined development
- βοΈ GitHub CI workflow with necessary automated checks:
composer lintβ ensures consistent code stylingcomposer rectorβ keeps your code up to datecomposer test.archβ architecture testingcomposer test.unitβ unit testscomposer test.featureβ feature tests with a minimum coverage check
- βοΈ Deploy wherever you want
- Production-ready
Dockerfile(using serversideup/docker-php) for containerized deployment - By default, the deploy job pushes image to AWS ECR repository. If you initiate an AWS compute service that supports container image (e.g. AppRunner, Lambda or EKS), deployment should work out-of-the-box just by configuring below variables in GitHub.
AWS_ACCESS_KEY_ID(secret)AWS_ECR_REGISTRY(secret)AWS_SECRET_ACCESS_KEY(secret)AWS_ECR_REPOSITORY(variable)AWS_REGION(variable)
- Modify
.github/workflows/200-cd.ymlif you don't want AWS containerized deployment.
- Production-ready
- βοΈ PestPHP configured with
Architecture,Unit&Featuretest-suites
- βοΈ IDE-Helper for autocompletion
- βοΈ Rector for effortless upgrades
- βοΈ Pint for code-styling
- βοΈ Larastan for static analysis, configured to
maxlevel
- βοΈ Check for consistent code-styling
- βοΈ Static analysis with
maxlevel - βοΈ Code-quality checks using rector
- βοΈ Strict models
- βοΈ Mandatory declaring strict types
- βοΈ Architecture tests β Laravel presets
- π‘ A few more that we can't mention here, with many more on the roadmap
You can easily modify this boilerplate to fit your specific requirements.
- Issues π for bugs
- PRs π for contributions (Fork the project and create MR targeting
mainbranch) - Discussions π for help, thoughts and suggestions
