Merge pull request #15 from Jackinatox/main

corrected reinstalling behaivior

Author: AjdinDev

docs/api/client/servers.md

@@ -1187,7 +1187,7 @@ curl -X POST "https://your-panel.com/api/client/servers/d3aac109/settings/reinst
 Returns empty response body with status code 202.
 
 :::warning Important
-Reinstalling a server will **permanently delete all files** and reinstall the server from scratch. Make sure to create backups before reinstalling.
+Reinstalling a server will just **rerun the install script** with all files still on the server. There is also no endpoint to delete all files.
 :::
 
 ### Update Docker Image
@@ -2006,7 +2006,7 @@ Trigger a reinstallation of the server. This will stop the server and re-run the
 **`POST /api/client/servers/{server}/settings/reinstall`**
 
 :::warning Important
-This action will delete all server files and reinstall the server from scratch. Make sure to backup important data before proceeding.
+Reinstalling a server will just **rerun the install script** with all files still on the server. There is also no endpoint to delete all files.
 :::
 
 ### URL Parameters

docs/rate-limiting.md

@@ -41,6 +41,28 @@ When you exceed the rate limit, you'll receive a `429 Too Many Requests` respons
 }
 ```
 
+## Increasing the Rate Limit
+
+You can configure the API rate limits on your Pterodactyl panel instance by editing the `.env` file. By default, these settings are not present, so you'll need to add them manually.
+
+The `.env` file is typically located at:
+
+```
+/var/www/pterodactyl/.env
+```
+
+Add or update the following lines to set your desired rate limits (values shown are defaults):
+
+```env
+APP_API_APPLICATION_RATELIMIT=240
+APP_API_CLIENT_RATELIMIT=240
+```
+
+- `APP_API_APPLICATION_RATELIMIT`: Sets the rate limit for the Application API (requests per minute per API key).
+- `APP_API_CLIENT_RATELIMIT`: Sets the rate limit for the Client API (requests per minute per API key).
+
+After making changes, restart your Pterodactyl panel for the new settings to take effect.
+
 ## Best Practices
 
 ### 1. Check Rate Limit Headers