2. Configuration
October 2, 2019 ยท View on GitHub
Table of contents
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-captchaand the file is located inapp/config/packages/arcanedev/no-captcha/config.php.