PHPackages thisisdevelopment/laravel-base - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [Framework](/categories/framework) 4. / 5. thisisdevelopment/laravel-base ActiveProject[Framework](/categories/framework) thisisdevelopment/laravel-base ============================== Opinionated Laraval base install 0.9.0(11mo ago)2136MITBladePHP ^8.2 Since Mar 9Pushed 11mo ago6 watchersCompare [ Source](https://github.com/thisisdevelopment/laravel-base)[ Packagist](https://packagist.org/packages/thisisdevelopment/laravel-base)[ RSS](/packages/thisisdevelopment-laravel-base/feed)WikiDiscussions master Synced 1mo ago READMEChangelog (1)Dependencies (12)Versions (23)Used By (0) thisisdevelopment/laravel-base ============================== [](#thisisdevelopmentlaravel-base) An opinionated base laravel install. Install ------- [](#install) ``` composer create-project thisisdevelopment/laravel-base ``` Or alternatively if you don't have composer installed locally: ``` dir= git clone https://github.com/thisisdevelopment/laravel-base $dir cd $dir rm -rf .git ./bin/dev init ``` Folder structure ---------------- [](#folder-structure) This is modeled after the domain oriented structure proposed by sticher.io: The proposed structure is extended with the concept of modules, which are default implementations of generic domain code. The complete structure is - `app` <= toplevel app dir, no code here - `app/App//` <= application specific code - `app/Domain/` <= domain specific code - `app/Domain/vendor/` <= generic domain code (managed by composer, for packages with type=laravel-domain) - `app/Module/` <= module code (managed by composer, for packages with type=laravel-module) - `packages//` <= composer wil automatically pickup any packages in this directory. This allows to develop packages alongside your application (see [packages/README.md](packages/README.md)) It uses `oomphinc/composer-installers-extender` to install packages of type laravel-module/laravel-domain to the `app/Module` and `app/Domain/vendor` folders. Docker compose support ---------------------- [](#docker-compose-support) This base install comes with a complete docker-compose setup out of the box. It assumes you have a working local docker install which allows access to docker for your own user. To easily access the containers you should also run the `thisisdevelopment/docker-hoster` container (see ) to dynamically update your hosts file. ``` docker run --restart=unless-stopped -d \ -v /var/run/docker.sock:/tmp/docker.sock \ -v /etc/hosts:/tmp/hosts \ thisisdevelopment/docker-hoster ``` Dev script ---------- [](#dev-script) To easily access the containers you should use the included `bin/dev` script. This script allows for easy execution of composer etc inside your containers. The supported commands are: - `up` - `down` - `rm` - `deploy` - `logs` - `php-cli` - `composer` - `artisan` - `phpcs` - `phpcbf` - `phpunit` Coding standards ---------------- [](#coding-standards) This base install enforces the `PSR-12` code standard. It does this by installing a git-hook which enforces this standard (by means of `phpcs`) SSL/HTTPS --------- [](#sslhttps) ### Linux [](#linux) To enable HTTPs on (Ubuntu) Linux, the following steps need to be performed. - generate local development certificate - rename app-hostname. - add nginx reverse proxy to docker-compose To generate a certificate you'll need the tool `mkcert` (to generate the certificate) and `libnss3-tools` to automatically register this certificate in your browser (Firefox/Chrome). e.g. `apt-get install mkcert libnss3-tools`. When installed, we can generate the certificate by running the following commands from project root, where `app.services.docker` needs to be replaced with the value from your `.env`'s `APP_DOMAIN`. ``` mkcert -key-file ./docker/services/app/certs/ssl.key -cert-file ./docker/services/app/certs/ssl.crt app.services.docker ``` Next, we need to add an additional service to the docker-stack, allowing us to use SSL. If not present already, create a `docker-compose.override.yml` at project root, and add the following. ``` services: nginx: image: nginx:latest hostname: $APP_DOMAIN depends_on: - app volumes: - ./docker/services/app/certs/:/etc/nginx/ssl - ./docker/services/app/nginx-ssl.conf:/etc/nginx/conf.d/app.services.docker.conf app: hostname: "" # this needs to be set to empty (or anything not APP_DOMAIN) to prevent collision with new nginx ``` Now you'll need to restart the entire stack with a `./bin/dev down && ./bin/dev up`. At this point the app should be available through https on the original domain. ### Mac [](#mac) Probably the easiest way to get https working is by using Orbstack using [these instructions](https://docs.orbstack.dev/features/https#https-for-containers). ### Environment [](#environment) For both Linux and Mac you need to set `VITE_APP_ORIGIN` to a url that includes `https` in the `.env` file.: - `VITE_APP_ORIGIN=https://${APP_DOMAIN}` Everything *should* work out of the box if you've followed the steps above, but you *might* need to update these environment variables in your `.env` as well: - `APP_HTTPS=true` - `APP_DOMAIN=https://${APP_DOMAIN}` ### Health Score 38 — LowBetter than 85% of packages Maintenance50 Moderate activity, may be stable Popularity13 Limited adoption so far Community11 Small or concentrated contributor base Maturity68 Established project with proven stability Bus Factor1 Top contributor holds 95.2% of commits — single point of failure How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window. **Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores. **Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement. **Maturity (30%)** — Project age, version count, PHP version support, and release stability. ### Release Activity Cadence Every ~100 days Recently: every ~177 days Total 20 Last Release 354d ago PHP version history (6 changes)0.1.0PHP ^7.2.5 0.5.0PHP ^7.4|^8.0 0.6.0PHP ^8.0.2 0.6.2PHP 8.0.x | 8.1.x | 8.2.x 0.7.0PHP ^8.1 0.8.0PHP ^8.2 ### Community Maintainers ![](https://www.gravatar.com/avatar/2e28c291bdd615f0334f50aef8fd3a08aa05283dfbc7e006b3b2bc6160804517?d=identicon)[ederuiter](/maintainers/ederuiter) --- Top Contributors [![ederuiter](https://avatars.githubusercontent.com/u/6728434?v=4)](https://github.com/ederuiter "ederuiter (20 commits)")[![dexmans](https://avatars.githubusercontent.com/u/254140?v=4)](https://github.com/dexmans "dexmans (1 commits)") --- Tags frameworklaravel ### Code Quality TestsPHPUnit Code StyleLaravel Pint ### Embed Badge ![Health badge](/badges/thisisdevelopment-laravel-base/health.svg) ``` [![Health](https://phpackages.com/badges/thisisdevelopment-laravel-base/health.svg)](https://phpackages.com/packages/thisisdevelopment-laravel-base) ``` ### Alternatives [juzaweb/cms Juzaweb CMS is a Content Management System (CMS) developed based on Laravel Framework and web platform whose sole purpose is to make your development workflow simple again. Project develop by Juzaweb 187571.2k](/packages/juzaweb-cms)[codewithdennis/larament Larament is a time-saving starter kit to quickly launch Laravel 13.x projects. It includes FilamentPHP 5.x pre-installed and configured, along with additional tools and features to streamline your development workflow. 3691.5k](/packages/codewithdennis-larament)[ercogx/laravel-filament-starter-kit This is a Filament v3 Starter Kit for Laravel 12, designed to accelerate the development of Filament-powered applications. 401.5k](/packages/ercogx-laravel-filament-starter-kit) PHPackages © 2026 [Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)