PHPackages techins-software/laravel-boilerplace - 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. techins-software/laravel-boilerplace ActiveProject[Framework](/categories/framework) techins-software/laravel-boilerplace ==================================== The skeleton application for the Laravel projects used upon techins https://techins.gr . v20250109090118(1y ago)021MITPHPPHP ^8.2 Since Sep 16Pushed 1y ago1 watchersCompare [ Source](https://github.com/TechIns-Software/laravel-boilerplace)[ Packagist](https://packagist.org/packages/techins-software/laravel-boilerplace)[ RSS](/packages/techins-software-laravel-boilerplace/feed)WikiDiscussions master Synced 1mo ago READMEChangelogDependencies (8)Versions (19)Used By (0) Laravel Boilerplate =================== [](#laravel-boilerplate) This is a boileplace code for admin panels used by our projects. It contains basic views and login functionality alongside with the nessesary files for deployment and testing. Upon frontend bootstrap is used. Create project: --------------- [](#create-project) ``` composer create-project techins-software/laravel-boilerplace my-new-project ``` Setup php dependencies ---------------------- [](#setup-php-dependencies) Create the nessesary .env file. If using our docker solution use the `.env.php_dev`: ``` cp .env.php_dev .env ``` > NOTE these credentials are viable if using the docker solution. It should NOT be used upon production Then once `.env` is generated run: ``` composer install php artisan key:generate php artisan migrate ``` Build Frontend -------------- [](#build-frontend) For development you can run: ``` npm install npm run build_dev ``` For onetime builds (or ci/cd ones) run: ``` npm install npm run build ``` Github actions & CI/CD -------------------------- [](#github-actions--cicd) The actions are used for: 1. Automated Tagging 2. Running Unit tests upon PR Look at `.github/workflows` folder for more info. Deployment & Building for release upon Server (CI/CD) --------------------------------------------------------- [](#deployment--building-for-release-upon-server-cicd) It contains, the following basic files for building the AWS codepipeline. Also it contains the following files for deployment: - `appspec.production.yml` For Deployment in a production traditional LEMP Stack - `appspec.staging.yml` For Deployment in a staging traditional LEMP Stack Also upon build the following files exist: - .env.production for bootstrapping environment upon production - .env.staging for bootstrapping environment upon staging Any secret values are and should be replaced upon `buildspec.yml` View templates -------------- [](#view-templates) All pages available for logged in users extend the `layout.layout-common` blade template. In case user is admin you can extend the `layout.layout-admin` one (it extends the `layout.layout-common` one placing nessesary links upon header). Feel free to place extra views and modify them as needed. The `layout.fullpage` is a layout that does NOT contain any header but only a single main item located as the center of the page, usefull for login and registration pages. Both `layout.layout-common` and `layout.fullpage` contain these sections you can place the nessesary html if needed: - `main` that main html resides - `nav-items` in which navigation items upon header are placed - `js` in which Javascript files are placed upon - `css` in which stylesheet is placed upon (NOT Available upon `layout.fullpage`) All templates use bootstrap and fontawesome. Javascript ---------- [](#javascript) All layouts extending `layout.layout-common`, by default load the `js/default.js` file. In case that a custom javascript file is needed then place the appropriate js file upon `resources/js` and upon the blade template and override the `js` section, look examples bellow. ### Example 1: overriding the default js with `resources/js/myjs.js` [](#example-1-overriding-the-default-js-with-resourcesjsmyjsjs) ``` @extends('layout.layout-common') @section('main') {{!! Your html content shown upon user !!}} @endsection @section('js') @vite(['resources/js/myjs.js']) @endsection ``` ### Example 2: Loading `resources/js/myjs.js` alongside the default js [](#example-2-loading-resourcesjsmyjsjs-alongside-the-default-js) ``` @extends('layout.layout-common') @section('main') {{!! Your html content shown upon user !!}} @endsection @section('js') @parent @vite(['resources/js/myjs.js']) @endsection ``` Css --- [](#css) There are the following css loaded bty Default upon each template: - `resources/css/common.css` => loaded by any template it loads bootstrap and fontawesome. - `resources/css/fullpage.css` => loaded by any template using `layout.fullpage` in includes `resources/css/common.css`. - `reources/css/user/list.css` => loaded by template `user.listUsers` it includes `resources/css/common.css`. In case you want to include your own css follow these steps: ### Create css files [](#create-css-files) First create the nessesary css file upon `resources/css`. Then place inside inside the following: ``` @import "resources/css/common.css"; /** rest of css goes here */ ``` ### Load 3rtd party css [](#load-3rtd-party-css) Furthermore if using a fullpage layout and want to place extra css on it you can do it: ``` @import "resources/css/fullpage.css"; /*Rest of css goes here*/ ``` You can use `@import` to import any 3rd party css as well if needed. Is css is installed via npm ensure that is placed upon `vite.config.js` file: [laravel-boilerplace/vite.config.js](https://github.com/TechIns-Software/laravel-boilerplace/blob/6331fb7a1b9238f8e9f193c80e872f116b90245c/vite.config.js#L40-L52) Lines 40 to 52 in [6331fb7](/TechIns-Software/laravel-boilerplace/commit/6331fb7a1b9238f8e9f193c80e872f116b90245c) const paths = \[ ...pageStyles, ...js, 'node\_modules/jquery/dist/jquery.js', "node\_modules/jscroll/dist/jquery.jscroll.min.js", 'node\_modules/bootstrap/dist/css/bootstrap.css', 'node\_modules/bootstrap/dist/js/bootstrap.bundle.js', 'node\_modules/@fortawesome/fontawesome-free/css/all.css', \] ### Load upon blade [](#load-upon-blade) Either case once you have your css ready you can load the file (assuming named as `resources/css/mycss.css`): ``` @section('css') @vite(['resources/css/mycss.css']) @endif ``` ### Build frontend [](#build-frontend-1) Then you can build the frontend as mentioned above: ``` npm run build_dev ``` ### Health Score 31 — LowBetter than 68% of packages Maintenance41 Moderate activity, may be stable Popularity3 Limited adoption so far Community9 Small or concentrated contributor base Maturity60 Established project with proven stability Bus Factor1 Top contributor holds 100% 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 ~7 days Recently: every ~27 days Total 18 Last Release 488d ago ### Community Maintainers ![](https://www.gravatar.com/avatar/d57c64b259195a64cbad626742deb35aa86219fdfebc2a3f40c23bb825ede735?d=identicon)[pc-magas](/maintainers/pc-magas) ![](https://www.gravatar.com/avatar/d2fb65a184a4f0a1e92faa3780a58049bd408c33446609f2ff0d68fd65f466fb?d=identicon)[ChristosBaztekas](/maintainers/ChristosBaztekas) --- Top Contributors [![pc-magas](https://avatars.githubusercontent.com/u/1299750?v=4)](https://github.com/pc-magas "pc-magas (24 commits)") --- Tags frameworklaravel ### Code Quality TestsPHPUnit Code StyleLaravel Pint ### Embed Badge ![Health badge](/badges/techins-software-laravel-boilerplace/health.svg) ``` [![Health](https://phpackages.com/badges/techins-software-laravel-boilerplace/health.svg)](https://phpackages.com/packages/techins-software-laravel-boilerplace) ``` ### Alternatives [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)