therealjanjanssens / pakka
pakka in a package
Fund package maintenance!
therealjanjanssens
Installs: 355
Dependents: 0
Suggesters: 0
Security: 0
Stars: 0
Watchers: 1
Forks: 1
Open Issues: 0
Language:Blade
Requires
- php: ^7.4|^8.0
- barryvdh/laravel-debugbar: ^3.2
- barryvdh/laravel-dompdf: ^0.9.0
- darryldecode/cart: dev-pakka
- fideloper/proxy: ^4.4
- fruitcake/laravel-cors: ^2.0
- illuminate/contracts: ^8.0
- laravel/framework: ^8.12
- laravel/tinker: ^2.5
- laravel/ui: ^3.2
- laravelcollective/html: ^6.2
- maatwebsite/excel: ^3.1
- mollie/laravel-mollie: ^2.14
- php-parallel-lint/php-console-highlighter: ^0.5.0
- phpmailer/phpmailer: ^6.2
- realrashid/sweet-alert: ^3.2
- spatie/laravel-analytics: ^3.10
- spatie/laravel-cookie-consent: ^2.12
- spatie/laravel-honeypot: ^3.0
- spatie/laravel-image-optimizer: ^1.6
- spatie/laravel-package-tools: ^1.9
- spatie/laravel-sitemap: ^5.9
- unikent/tfilecache: dev-pakka
Requires (Dev)
- nunomaduro/collision: ^5.3
- orchestra/testbench: ^6.0
- pestphp/pest: ^1.18
- pestphp/pest-plugin-laravel: ^1.1
- dev-master
- 1.1.6
- 1.1.5
- 1.1.4
- 1.1.3
- 1.1.2
- 1.1.1
- 1.1.0
- 1.0.6
- 1.0.5
- 1.0.4
- 1.0.3
- 1.0.2
- 1.0.1
- 1.0.0
- 0.4.2
- 0.4.1
- 0.4.0
- 0.3.7
- 0.3.6
- 0.3.5
- 0.3.4
- 0.3.3
- 0.3.2
- 0.3.1
- 0.3.0
- 0.2.6
- 0.2.5
- 0.2.4
- 0.2.3
- 0.2.2
- 0.2.1
- 0.2.0
- 0.1.7
- 0.1.6
- 0.1.5
- 0.1.4
- 0.1.3
- 0.1.2
- 0.1.1
- 0.1.0
- 0.0.5
- 0.0.4
- 0.0.3
- 0.0.2
- 0.0.1
- dev-feature/tailwind-admin-panel
- dev-hotfix/1.0.6
- dev-feature/livewire-forms
- dev-refactor/input-builder
- dev-refactor/relationships
This package is auto-updated.
Last update: 2024-11-05 09:53:02 UTC
README
Pakka in a package
Installation
You can install the package via composer:
composer require therealjanjanssens/pakka
We also prepared a complete setup for the pakka package with following command
php artisan pakka-install
You can publish the config file with:
php artisan vendor:publish --provider="TheRealJanJanssens\Pakka\PakkaServiceProvider" --tag="config"
Installation for development
Provide this info for this section.
Upgrade guide
Database structure changes
When changing something on the structure of the database please do it with migrations and create a new stub so updating instances will be easier. Take add_permission_to_section_items_table.php.stub as example when dealing with columns and create_attribute_inputs_table.php.stub when dealing with tables
Upgrading to 1.0 From 0.x
When updating everything below 1.0.0 to current version take a backup from the database and remove the existing database. Reconstruct it with php artisan pakka-install and insert the data back into it
Testing
Use below commands to run the Unit tests
composer test
or
./vendor/bin/pest tests
If you want to run the tests like its getting triggered with Github actions first make sure you have docker installed and install arc
brew instal act
Once everything is installed you can simulate the Github actions with:
or
act -P ubuntu-latest=shivammathur/node:latest
Custom sections, templates and layouts
If you need to change a particular section, template or layout you can simply add a 'sections', 'templates' or 'layouts' folder in your views. You can put a copy of existing resources in the folder you just made and do all the changes you want. When you update the package this folder won't be updated so your custom resources will be untouched.
Custom sections also can have their own custom thumbnail. Just add the following to your project and your set!
"/public/images/sections/{nameSection}.png"
Custom dynamic sections with items
This sounds a bit abstract but you can put custom html/blade in a few selected sections (For example IFRMST01004). Some of them even allow you to connect a item module to them and directly list items in your custom html/blade. To access the item variables you just use the name of the key as variable like:
$item['title'] => $title
$item['description'] => $description
...
Changelog
Please see CHANGELOG for more information on what has changed recently.
Contributing
Please see CONTRIBUTING for details.
Security Vulnerabilities
Please review our security policy on how to report security vulnerabilities.