# Laravel specific settings

{% hint style="warning" %}
Please be sure of your agent type and version and pick the right documentation accordingly.
{% endhint %}

{% tabs %}
{% tab title="Node.js" %}
{% hint style="danger" %}
This is the documentation of the `forest-express-sequelize` and `forest-express-mongoose` Node.js agents that will soon reach end-of-support.

`forest-express-sequelize` v9 and `forest-express-mongoose` v9 are replaced by [`@forestadmin/agent`](https://docs.forestadmin.com/developer-guide-agents-nodejs/) v1.

Please check your agent type and version and read on or switch to the right documentation.
{% endhint %}
{% endtab %}

{% tab title="Ruby on Rails" %}
{% hint style="success" %}
This is still the latest Ruby on Rails documentation of the `forest_liana` agent, you’re at the right place, please read on.
{% endhint %}
{% endtab %}

{% tab title="Python" %}
{% hint style="danger" %}
This is the documentation of the `django-forestadmin` Django agent that will soon reach end-of-support.

If you’re using a Django agent, notice that `django-forestadmin` v1 is replaced by [`forestadmin-agent-django`](https://docs.forestadmin.com/developer-guide-agents-python) v1.

If you’re using a Flask agent, go to the [`forestadmin-agent-flask`](https://docs.forestadmin.com/developer-guide-agents-python) v1 documentation.

Please check your agent type and version and read on or switch to the right documentation.
{% endhint %}
{% endtab %}

{% tab title="PHP" %}
{% hint style="danger" %}
This is the documentation of the `forestadmin/laravel-forestadmin` Laravel agent that will soon reach end-of-support.

If you’re using a Laravel agent, notice that `forestadmin/laravel-forestadmin` v1 is replaced by [`forestadmin/laravel-forestadmin`](https://docs.forestadmin.com/developer-guide-agents-php) v3.

If you’re using a Symfony agent, go to the [`forestadmin/symfony-forestadmin`](https://docs.forestadmin.com/developer-guide-agents-php) v1 documentation.

Please check your agent type and version and read on or switch to the right documentation.
{% endhint %}
{% endtab %}
{% endtabs %}

## Laravel specific settings

#### Publish the configuration

If you would like to publish the configuration of the package, you can run the following command:

```php
php artisan vendor:publish --provider="ForestAdmin\LaravelForestAdmin\ForestServiceProvider" --tag=config
```

#### Send apimap on deploy

When you want to deploy your forest admin to production (or other branch different of your local environment), you must run the following command:

```php
php artisan forest:send-apimap
```

This command must be run each time you deploy your application on production.

But you can avoid it and activate the mode "apimap send auto" with the environment variable `FOREST_SEND_APIMAP_AUTOMATIC`.

You have 2 solutions:

* add `FOREST_SEND_APIMAP_AUTOMATIC` to your .env file and set to true
* publish your configuration and set to true the `send_apimap_automatic` into `config/forest.php`

However, beware that if you activate this configuration, you must refresh your forest dashboard after you deploy on production.

{% hint style="info" %}
Depending on your configuration, refreshing the whole application may take a few seconds after your deployment. Using the environment variable is recommended for small projects, whereas the php artisan command is better suited when dealing with bigger projects.
{% endhint %}

#### Onboard with Laravel Valet

When using Laravel Valet, you must configure to SSL.

```
valet secure YOUR_PROJECT_NAME
```

Then declare the corresponding url in your .env file into the APP\_URL variable.

{% hint style="info" %}
Don't forget the S of https
{% endhint %}

```
APP_URL=https://YOUR_PROJECT_NAME.test
```

{% hint style="warning" %}
With Laravel Valet the apimap is not updated automatically. We recommend that you set your environment variable FOREST\_SEND\_APIMAP\_AUTOMATIC to true. More information in the previous chapter [Send apimap on deploy](#send-apimap-on-deploy)
{% endhint %}

#### Customize models directory structure

The agent fetches the models into the directory specified by the `models_directory` configuration.

{% hint style="info" %}
All class files that doesn't extends the Illuminate\Database\Eloquent\Model are ignored.
{% endhint %}

By default, the value is the main models directory of Laravel 'app/Models', but you can change this configuration and add one or more models directories.

Example

```php
'models_directory'    => ['app/StripeModels', 'app/CustomerModels'],
```

You don't have to specify all the subdirectories, the agent will retrieve them for you. For example, imagine with the directory structure : `app/StripeModels/Billing` & `app/StripeModels/Orders`, you have just to specify the main directory `app/StripeModels`.

You can also include/exclude models. More information [here](https://docs.forestadmin.com/documentation/how-tos/settings/include-exclude-models)
