Update additional_configuration.md (#317)

* Fix query and remove unnecessary s3 settings

Remove s3 accelerate and style_endpoint as they're already set to false by default.

Fix Recaptcha required env setting and MySQL query typo together with shrinking it into a one-liner

* Remove .env section

* Removes the last mention of .env

* this is the last one I promise
This commit is contained in:
Alex 2021-02-15 02:04:23 +02:00 committed by GitHub
parent 854b16f899
commit b8165980b2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -20,10 +20,6 @@ AWS_ACCESS_KEY_ID=
AWS_SECRET_ACCESS_KEY=
AWS_BACKUPS_BUCKET=
AWS_ENDPOINT=
AWS_BACKUPS_USE_ACCELERATE=false
# This was/is planned to be depreciated by AWS thus if set to true it will fail the request.
AWS_USE_PATH_STYLE_ENDPOINT=false
```
## reCAPTCHA
@ -48,26 +44,12 @@ If users have trouble logging in, or your Panel isn't exposed to the internet, i
reCAPTCHA can easily be disabled using the admin panel. In the Settings, select the **Advanced** tab and set the **Status** of reCAPTCHA to **disabled**.
#### Using the .env file
If you cannot access the panel yourself, you can also disable reCAPTCHA using the `.env` file.
```
RECAPTCHA_ENABLED=false
```
#### Editing your database
:::danger DANGEROUS: Not Recommended
Proceed carefully. By running queries on your database directly, you can easily break your setup.
:::
If you cannot access your panel, but have used the web panel based settings already, you can modify the database directly using the following commands.
If you cannot access your panel, you can modify the database directly using the following commands.
```sql
mysql -u root -p
USE panel;
UPDATE settings SET value = 'false' WHERE 'key' = 'settings::recaptcha:enabled';
UPDATE panel.settings SET value = 'false' WHERE `key` = 'settings::recaptcha:enabled';
```
If the command returns with `Query OK, 0 rows affected (0.000 sec)` you need to use the `.env` method to disable reCAPTCHA