Configuration

Conduit comes with a default, recommended set of configuration files, however, you can publish these to your Laravel application and customize them.

Publishing the Configuration

To publish the configuration, run this command:

1phpartisanvendor:publish--provider="Mergeloop\Conduit\ConduitServiceProvider"--tag=config--force

This will publish a conduit.php file inside your app/config directory. From here, you may edit either file to customize the site to your needs.

It's also important to note that you can remove any of the configuration keys from conduit.php that you are not customizing, this will allow to streamline your configuration file because Laravel will default to the configuration file within the Autoload package itself.

Customizations

The conduit.php config file follows standard Laravel config file conventions, therefore can be accessed the same way.

Each key within the config file's array can be fetched via config('conduit.KEY_NAME'). These keys are named appropriately to what they do within Conduit; such as;

• user = resolves the primary User model for the application

and so on. Full details on all configurations below.

All Configuration Options

• conduit_license_token = The license token for your Conduit installation.
• payment_provider = Either Stripe or Paddle, but will default to whichever keys you have in your .env file.
• frontend_provider = Either Blade or Livewire (coming soon)
• user = The Laravel User Model that will be used for authentication
• cart.name = The name of the cookie that will be used to store the cart data for guest users.
• cart.ttl = The time-to-live for said cart cookie. Default is 1 week.
• analytics.google = environment variable for Google Analytics that will be used on the Account and Cart pages.
• analytics.fathom = environment variable for Fathom Analytics that will be used on the Account and Cart pages.