2-Configuration.md

2. Configuration

Table of contents

1. Installation and Setup
2. Configuration
3. Usage
4. Extras
5. FAQ

There is not really a need to publish the configuration file. Both the secret and sitekey should be set in your environment file so it won't be available in your versioning system.

Option 1 - Environment Configuration:

See Environment Configuration documentation.

// Edit your .env file by adding this two lines and fill it with your keys.

NOCAPTCHA_SECRET=your-secret-key
NOCAPTCHA_SITEKEY=your-site-key

For Laravel 4.2: Protecting Sensitive Configuration

Option 2 - Publish configuration file:

Run php artisan vendor:publish --provider="Arcanedev\NoCaptcha\NoCaptchaServiceProvider" to publish the config file.

Edit the secret and sitekey values in config/no-captcha.php file:

For Laravel 4.2, run php artisan config:publish arcanedev/no-captcha and the file is located in app/config/packages/arcanedev/no-captcha/config.php.