This is where your description should go. Limit it to a paragraph or two. Consider adding a small example.
You can install the package via composer:
composer require teamtnt/sales-managementYou can publish and run the migrations with:
php artisan vendor:publish --tag="sales-management-migrations"
php artisan migrateYou can publish the config file with:
php artisan vendor:publish --tag="sales-management-config"This is the contents of the published config file:
return [
];Optionally, you can publish the views using
php artisan vendor:publish --tag="sales-management-views"Publishing assets
php artisan vendor:publish --tag="sales-management-assets"We use Vite to build assets. First install all dependencies.
npm installIf there is no public folder in project root run first production build which will build needed folders:
npm run buildDevelopment build:
npm run devFor local development to have hot reloading create a symlink
ln -s ../vendor/teamtnt/sales-management/public/sales-management public/sales-managementAdd to composer.json
"repositories": [{
"type": "path",
"url": "../sales-management"
}],
"require": {
"teamtnt/sales-management": "@dev"
}
$salesManagement = new Teamtnt\SalesManagement();
echo $salesManagement->echoPhrase('Hello, Teamtnt!');composer testPlease see CHANGELOG for more information on what has changed recently.
Please see CONTRIBUTING for details.
Please review our security policy on how to report security vulnerabilities.
The MIT License (MIT). Please see License File for more information.