-
Notifications
You must be signed in to change notification settings - Fork 3
Project Configuration
Before starting with the installation, some configuration might be made to the Laravel project where Tendoo CMS is installed as a package.
Tendoo CMS has his own User Model build-in. In order for some feature to work properly, you need to configure the default User Model used on the Laravel Project at config/auth.php.
You'll then have to change the providers key on the auth configuration like so :
<?php
return [
/**
* ... Ignore previous keys
**/
'providers' => [
'users' => [
'driver' => 'eloquent',
'model' => Tendoo\Core\Models\User::class
],
],
]Tendoo CMS has his own way to handle errors. This error handler has been made to display errors for production projects and to display a more accurate details for the system errors.
In order to add support for theses errors, your App\Http\Exceptions\Handler must extends Tendoo\Core\Exceptions\TendooHandler which already extends Illuminate\Foundation\Exceptions\Handler.
<?php
namespace App\Exceptions;
use Exception;
use Tendoo\Core\Exceptions\TendooHandler;
class Handler extends TendooHandler
{
// ... Tendoo CMS uses Bootstrap 4 Material and other assets dependencies. They needs to be published in order to use the project correctly. Use the default Laravel command to publish vendors like so :
php artisan vendor:publish
The assets are located under the following tags :
- tendoo-assets
- tendoo-config
If you're using the project locally and have not yet setup an mail provider, then we encourage you to change the provider by default on the .env file.
You can then set the value "MAIL_DRIVER" to 'log' like so :
MAIL_DRIVER=log
Once that you're done with this, you're ready to get started. All you have to do is to serve the project if you're running locally :
php artisan serve
Or to access directly to the project remotely.