README

This is where your description should go. Limit it to a paragraph or two. Consider adding a small example.

Installation

You can install the package via composer:

composer require teamtnt/sales-management

You can publish and run the migrations with:

php artisan vendor:publish --tag="sales-management-migrations"
php artisan migrate

You 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"

Building Assets

We use Vite to build assets. First install all dependencies.

npm install

If there is no public folder in project root run first production build which will build needed folders:

npm run build

Development build:

npm run dev

For local development to have hot reloading create a symlink

ln -s ../vendor/teamtnt/sales-management/public/sales-management public/sales-management

Add to composer.json

    "repositories": [{
        "type": "path",
        "url": "../sales-management"
    }],
    "require": {
        "teamtnt/sales-management": "@dev"
    }

Usage

$salesManagement = new Teamtnt\SalesManagement();
echo $salesManagement->echoPhrase('Hello, Teamtnt!');

Testing

composer test

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.

Credits

License

The MIT License (MIT). Please see License File for more information.

teamtnt / sales-management

Maintainers

Details