mirror of
https://github.com/pterodactyl/documentation.git
synced 2025-12-10 10:44:43 -06:00
More grammar fixes
This commit is contained in:
parent
4f5c334ddd
commit
068d5d50c8
@ -1,9 +1,9 @@
|
|||||||
# Customizing Wings
|
# Customizing Wings
|
||||||
:::warning Production
|
:::warning Production
|
||||||
We highly recommend **NOT** performing these actions on production
|
We highly recommend **NOT** performing these actions on the production
|
||||||
:::
|
:::
|
||||||
|
|
||||||
In order to make changes to wings we recommend forking it to keep your own git version making upgrades easier. <br />
|
We recommend creating a fork of the repo before making changes to wings to make future upgrades easier. <br />
|
||||||
:::tip Editing Files
|
:::tip Editing Files
|
||||||
We do not provide a guide at the current time on what files to edit to get certain results. This guide expects a basic knowledge of the `Go` language
|
We do not provide a guide at the current time on what files to edit to get certain results. This guide expects a basic knowledge of the `Go` language
|
||||||
:::
|
:::
|
||||||
@ -17,7 +17,7 @@ By default, Go targets the system it is executed on. Therefore, the easiest way
|
|||||||
You need to have an up-to-date version of the Go tools installed. See the [official instructions](https://golang.org/doc/install) for help with setting those up.
|
You need to have an up-to-date version of the Go tools installed. See the [official instructions](https://golang.org/doc/install) for help with setting those up.
|
||||||
|
|
||||||
### Building
|
### Building
|
||||||
Running the following command in your local clone of the repository to compile wings into a binary.
|
Execute the following command in your local clone of the repository to compile wings into a binary.
|
||||||
```bash
|
```bash
|
||||||
go build
|
go build
|
||||||
```
|
```
|
||||||
@ -25,7 +25,7 @@ You should now have a `wings` binary file in your wings directory.
|
|||||||
## Install the new binary
|
## Install the new binary
|
||||||
|
|
||||||
:::tip Root required
|
:::tip Root required
|
||||||
In order to execute the next few commands, you will need root permissions. If you are not logged in as root, either use `sudo` in front of each command, or run `sudo -i` to switch to a root session.
|
To execute the next few commands, you will need root permissions. If you are not logged in as root, either use `sudo` in front of each command, or run `sudo -i` to switch to a root session.
|
||||||
:::
|
:::
|
||||||
|
|
||||||
1. Backup the current installation of wings
|
1. Backup the current installation of wings
|
||||||
@ -37,6 +37,6 @@ systemctl stop wings
|
|||||||
mv /usr/local/bin/wings /usr/local/bin/wings-backup
|
mv /usr/local/bin/wings /usr/local/bin/wings-backup
|
||||||
```
|
```
|
||||||
2. Place the new binary in `/usr/local/bin`
|
2. Place the new binary in `/usr/local/bin`
|
||||||
3. Ensure aproperiate permissions on the binary `chmod u+x /usr/local/bin/wings`
|
3. Ensure appropriate permissions on the binary `chmod u+x /usr/local/bin/wings`
|
||||||
4. Try running the updated binary from the console `wings --debug`
|
4. Try running the updated binary from the console `wings --debug`
|
||||||
5. Restore normal operation of Wings `systemctl enable wings --now`
|
5. Restore normal operation of Wings `systemctl enable wings --now`
|
||||||
|
|||||||
@ -1,13 +1,13 @@
|
|||||||
# Disabling reCAPTCHA
|
# Disabling reCAPTCHA
|
||||||
|
|
||||||
:::warning SECURITY WARNING
|
:::warning SECURITY WARNING
|
||||||
It is highly reccomended to keep reCAPTCHA enabled, as reCAPTCHA is a security method that can protect your site from some methods of attack!
|
It is highly recommended to keep reCAPTCHA enabled, as reCAPTCHA is a security method that can protect your site from some methods of attack!
|
||||||
Only continue if you intend to re-enable reCAPTCHA after fixing whatever issue you may have!
|
Only continue if you intend to re-enable reCAPTCHA after fixing whatever issue you may have!
|
||||||
:::
|
:::
|
||||||
|
|
||||||
## Disabling via .env
|
## Disabling via .env
|
||||||
|
|
||||||
In order to disable reCAPTCHA using this method, you need to find and edit your `.env` file, It is usually located at `/var/www/pterodactyl/.env`
|
To disable reCAPTCHA using this method, you need to find and edit your `.env` file, It is usually located at `/var/www/pterodactyl/.env`
|
||||||
|
|
||||||
:::tip Hidden Files
|
:::tip Hidden Files
|
||||||
In linux, files starting with a `.` are considered to be hidden, so most FTP software may not show it by default. You can see the file by using `ls -a`
|
In linux, files starting with a `.` are considered to be hidden, so most FTP software may not show it by default. You can see the file by using `ls -a`
|
||||||
@ -21,6 +21,10 @@ cp .env .env.bkp
|
|||||||
|
|
||||||
You can now edit the `.env` file using your favorite editor to set the fields below
|
You can now edit the `.env` file using your favorite editor to set the fields below
|
||||||
|
|
||||||
|
:::tip Missing Values
|
||||||
|
If any of the bellow values are missing from your `.env` file you can add them yourself
|
||||||
|
:::
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
# Ignores database settings
|
# Ignores database settings
|
||||||
APP_ENVIRONMENT_ONLY=true
|
APP_ENVIRONMENT_ONLY=true
|
||||||
|
|||||||
@ -22,7 +22,8 @@ AWS_BACKUPS_BUCKET=
|
|||||||
|
|
||||||
AWS_ENDPOINT=
|
AWS_ENDPOINT=
|
||||||
|
|
||||||
# Dunno what these are but maybe you do?
|
|
||||||
AWS_USE_PATH_STYLE_ENDPOINT=false
|
|
||||||
AWS_BACKUPS_USE_ACCELERATE=false
|
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
|
||||||
```
|
```
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user