Package Data | |
---|---|
Maintainer Username: | trigger |
Maintainer Contact: | trigve.hagen@gmail.com (Trigve-Hagen) |
Package Create Date: | 2017-03-13 |
Package Last Update: | 2017-05-12 |
Language: | PHP |
License: | MIT |
Last Refreshed: | 2024-11-19 03:12:38 |
Package Statistics | |
---|---|
Total Downloads: | 18 |
Monthly Downloads: | 0 |
Daily Downloads: | 0 |
Total Stars: | 3 |
Total Watchers: | 2 |
Total Forks: | 0 |
Total Open Issues: | 0 |
PLEASE USE ON A NEW INSTALL OF LARAVEL FIRST TILL YOU UNDERSTAND HOW IT WORKS. - WHEN FIRST PUT INTO USE IT WILL ERASE ANYTHING DONE BEFORE IT AND CREATE A SAMPLE USER DATABASE Go into the root of your Laravel installation and run composer require trigves/arm from the command line. Add Trigves\Arm\ArmServiceProvider:class, to the providers array in config/app.php, fill in you database credentials in .env and run php artisan vendor:publish from your root. It will create an arm.php in the config folder where you can manage the tablesArray from. You will have to build your application from the array from there on out. It does not work with make:auth or Voyager. Out of the box it will automatically create the users table by default but you can erase it by erasing it from the tablesArray. I left it in there as and example because you have to follow the naming conventions. It builds it the moment you publish. Build the tablesArray in the same style but add your own names and fields. The first two fields are the table name, the unique auto increment id. They have to be in the array. The created_at and the updated_at are optional but some servers only allow one. The rest are also optional. They can be changed to VARCHAR TEXT INT etc.. For the moment this class is a stand alone project and has not been configured to work with Voyager or Artisan commands. There is some overhead in page load time when in development. When you go to production comment out the Service in the providers array in config/app.php and the load time will go back to normal.
YOU REALLY HAVE TO WATCH WHEN YOU ARE CREATING YOUR TABLES AND FIELDS
I take no responsibility for lost data! Use at your risk. Happy Coding!!
INSTALLATION
3/10/2017 - updates
3/13/2017 - updates