Skip to content

Commit 4580075

Browse files
committed
updates to final docs fixed some broken links tested build deployment
1 parent 6a6707c commit 4580075

42 files changed

Lines changed: 250 additions & 54 deletions

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

README.md

Lines changed: 52 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -1,23 +1,64 @@
11
# TCAdmin Documentation
22

3-
Welcome to the official documentation for TCAdmin! This repository contains comprehensive documentation for TCAdmin, a leading control panel for game server hosting. This README provides an overview of the documentation structure and how to contribute to its improvement.
3+
Welcome to the TCAdmin documentation repository! This repository contains comprehensive documentation for various aspects of the TCAdmin platform. Whether you're new to TCAdmin or an experienced user, this guide will walk you through different processes and functionalities.
44

5-
## Table of Contents
5+
## Getting Started with GitHub Desktop
66

7-
**TO DO STILL**
7+
To contribute to the TCAdmin documentation using GitHub Desktop, follow these steps:
88

9-
## About TCAdmin
9+
### 1. Fork the Repository
1010

11-
TCAdmin is a powerful and user-friendly control panel designed for game server administrators and hosting providers. It offers a wide range of features to simplify the management of game servers, including server deployment, configuration, monitoring, and more. With TCAdmin, you can easily manage multiple game server instances, control access and permissions, and provide an intuitive user interface for your customers.
11+
1. Click the "Fork" button at the top right corner of this repository. This action will create a copy of the repository in your GitHub account.
1212

13-
For more information about TCAdmin, please visit the [official website](https://www.tcadmin.com/).
13+
### 2. Clone the Repository
1414

15-
## Documentation Structure
15+
1. Download and install [GitHub Desktop](https://desktop.github.com/) if you haven't already.
16+
2. Click the "Clone a repository" button in GitHub Desktop.
17+
3. Select the "tcadmin-docs" repository from the list and choose a local path where you want to clone the repository.
1618

17-
The TCAdmin documentation is organized into the following main sections:
19+
### 3. Make Changes
1820

19-
**TO DO STILL**
21+
1. Open the cloned repository in GitHub Desktop.
22+
2. Create a new branch for your changes by clicking on the "Current branch" dropdown and selecting "New Branch." Give your branch a descriptive name related to the changes you'll be making.
23+
3. Make the necessary updates to the documentation using your preferred text editor.
2024

21-
## Contributing
25+
### 4. Commit and Push Changes
2226

23-
We welcome contributions to enhance the TCAdmin documentation. If you find any errors, typos, or missing information, or if you would like to propose improvements
27+
1. After making changes, return to GitHub Desktop.
28+
2. You will see your changes listed under "Changes."
29+
3. Add a summary and description of your changes in the provided fields.
30+
4. Click the "Commit to \<branch name\>" button to commit your changes to the new branch.
31+
5. Click the "Push origin" button to push your changes to your forked repository on GitHub.
32+
33+
### 5. Create a Pull Request
34+
35+
1. After pushing your changes, you'll see a banner in GitHub Desktop suggesting you create a pull request. Click the "Create Pull Request" button.
36+
2. This action will open your web browser and take you to the pull request page on GitHub. Provide a clear title and description for your pull request, summarizing the changes you've made.
37+
38+
### 6. Review and Merge
39+
40+
Our team will review your pull request, offer feedback if necessary, and once everything looks good, your changes will be merged into the main documentation repository.
41+
42+
Thank you for contributing to the TCAdmin documentation!
43+
44+
## Additional Notes
45+
46+
- Please follow the [Markdown style guide](https://www.markdownguide.org/basic-syntax/) when writing and formatting documentation content.
47+
48+
- For any questions or assistance, feel free to reach out to us by creating an issue in this repository.
49+
50+
## How to Submit an Issue or Suggestion
51+
52+
To submit an issue or suggestion, please follow these steps:
53+
54+
1. **Check for existing issues**: Before submitting a new issue or suggestion, please search the tracker to ensure that it hasn't been reported or suggested before. This helps us avoid duplicates and allows us to focus on resolving unique problems and implementing new ideas.
55+
56+
2. **Create a new issue**: If you couldn't find a similar issue or suggestion, click on the ["Issues"](../../issues) tab above and then click the ["New Issue"](../../issues/new/choose) button. Provide a descriptive title that summarizes the problem or suggestion concisely.
57+
58+
3. **Provide details**: In the issue description, provide as much information as possible to help us understand the problem or suggestion. Include clear steps to reproduce the issue or a detailed explanation of the enhancement you're suggesting. You can also attach relevant screenshots or files to support your submission.
59+
60+
4. **Label and assign**: Once you've created the issue, please assign the appropriate labels that best categorize the problem or suggestion. This helps us organize and prioritize the issues accordingly. If you're a team member responsible for managing this tracker, you can assign the issue to yourself or the relevant person for further action.
61+
62+
5. **Engage in discussion**: Feel free to engage in the discussion by providing additional details, asking questions, or clarifying any points raised by other community members or our team. Your input is valuable, and together we can find the best solutions and ideas.
63+
64+
6. **Track progress**: As we work on addressing the issues or implementing the suggestions, we will update the status and provide relevant comments. You can subscribe to notifications to stay informed about the progress.

docs/billing-api/tcadmin2-advanced-module-for-whmcs.mdx

Lines changed: 67 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -320,4 +320,70 @@ case "2GB":
320320
- Change the value of package_id to the id of the package you want to assign.
321321
- Select your reseller product in WHMCS. In the module settings tab set the config file to reseller.php
322322

323-
### Other configuration parameters
323+
### Other configuration parameters
324+
325+
- **game_start / voice_start**
326+
- Start the service after it has been created.
327+
- Allowed values are 1 and 0.
328+
- The default value is 1.
329+
330+
- **game_startup / voice_startup**
331+
- Specify the service's startup.
332+
- Allowed values are Automatic, Manual, Disabled.
333+
- The default value is Automatic.
334+
335+
- **game_additional_slots / voice_additional_slots**
336+
- Value added to game_slots.
337+
- Default value is 0.
338+
339+
- **game_priority / voice_priority**
340+
- Specify the CPU priority.
341+
- Allowed values are Idle, BelowNormal, Normal, AboveNormal, High, RealTime.
342+
- The default value is Normal.
343+
344+
- **game_server / voice_server**
345+
- Specify the server id for service creation.
346+
- Can be used instead of game_datacenter.
347+
348+
- **game_cpu / voice_cpu**
349+
- Specify a value from 1 to 100 (Windows) or 1 to (100 x number of processors) (Linux).
350+
- See [Limit Service CPU and Memory Usage **(Windows)**](/misc/limit-service-cpu-andmemory-usage#windows).
351+
- See [Limit Service CPU and Memory Usage **(Linux)**](/misc/limit-service-cpu-andmemory-usage#linux).
352+
353+
- **game_memory / voice_memory**
354+
- Specify the max allowed memory in MB.
355+
356+
- **game_virtual_memory / game_virtual_memory**
357+
- Specify the max allowed virtual memory in MB (Windows only).
358+
359+
### Specifying Different Module Value and Display Value
360+
361+
In WHMCS, you can configure dropdowns and radios to send a different value to the module than the one that is displayed in the order form. This is useful because you must send ids to the TCAdmin billing api but you want to show a friendly name to the client. The module value and display value are separated by the pipe character "|". The format is ModuleValue|DisplayValue For example: You can create a dropdown list that has the locations New York and Dallas but you want the billing api to receive the datacenter ids 1 and 2. You can create a `Custom Field` of type `Drop Down` with these options: 1|Dallas,2|NewYork
362+
363+
### Troubleshooting
364+
365+
- The values sent to TCAdmin are saved in the log file `/home/tcadmin/Logs/Web/BillingApi.LastCommand.log` or `C:\Program Files\TCAdmin2\Logs\Web\BillingApi.LastCommand.log` Make sure TCAdmin is receiving the correct values. The values required to create a game server are: game_id, game_slots, game_datacenter.
366+
- If TCAdmin accepts the values a scheduled task is created. If the game server is never created go to System > General Settings > Scheduled Tasks. Select the Day view and click on the task that was created. You should see the error message preventing the game server from being created. Correct the problem and start the task again. You don't need to send the command from WHMCS again.
367+
368+
### Update Products and Services from tcadmin to tcadmin2_advanced
369+
370+
If you are going to keep the same custom fields and configurable options in your products you need to follow these steps:
371+
- Update the module settings in the product. Switch from tcadmin to tcadmin2_advanced module and map the required tcadmin attributes to custom fields and configurable options.
372+
- Update the server field in the client's service.
373+
374+
If you are going to change custom fields and configurable options we recommend you create a copy of the product and modify the copy (Duplicate link at the top of the products page). When the new product is ready go to the client's service. Change the package and server. Enter the correct values again and save.
375+
376+
:::warning warning
377+
After you change the package all the values of custom fields and configurable options for that service will be lost and you will not be able to recover them.
378+
:::
379+
380+
To enable direct client login from WHMCS to TCAdmin you must configure the service’s username and password. To disable this feature leave the username and password fields blank.
381+
382+
### Cloudflare
383+
384+
If Cloudflare is blocking requests to the billing api go to the `Cloudflare control panel` > Security > Web Application Firewall (WAF) > Tools and allow your WHMCS IP.
385+
386+
![WHMCS_WAF](/img/billing-api/WHMCS_WAF.png)
387+
388+
![WHMCS_WAF2](/img/billing-api/WHMCS_WAF2.png)
389+

docs/customizations/modules/sample-module.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This is an example of a module that can be installed onto your master which will
1111

1212
### Sample View Page - HelloWorld.cshtml
1313

14-
```html showLineNumbers
14+
```cshtml showLineNumbers
1515
@model Game.HelloWorldModel
1616
@{
1717
Layout = this.GetTemplateFile("Shared/Main.cshtml", true);

docs/customizations/scripts/custom-protocols/_category_.json

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"label": "Custom Protocols",
3-
"position": 2,
3+
"position": 3,
44
"link": {
55
"type": "generated-index",
66
"description": "TCAdmin Custom Protocols"
Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,8 @@
1+
{
2+
"label": "General Scripts",
3+
"position": 1,
4+
"link": {
5+
"type": "generated-index",
6+
"description": "General Scripts for TCAdmin"
7+
}
8+
}

docs/customizations/scripts/allow-user-to-change-exe.mdx renamed to docs/customizations/scripts/general-scripts/allow-user-to-change-exe.mdx

File renamed without changes.

docs/customizations/scripts/allow-user-to-change-slots.mdx renamed to docs/customizations/scripts/general-scripts/allow-user-to-change-slots.mdx

File renamed without changes.

docs/customizations/scripts/automatically-create-mysql-database.mdx renamed to docs/customizations/scripts/general-scripts/automatically-create-mysql-database.mdx

File renamed without changes.

docs/customizations/scripts/backup-restore-scripts-with-ftp-support.mdx renamed to docs/customizations/scripts/general-scripts/backup-restore-scripts-with-ftp-support.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,12 +6,12 @@ sidebar_label: Backup & Restore Scripts with FTP Support
66
# Backup & Restore Scripts with FTP Support
77

88
:::info
9-
These scripts are a modified version of [Backup & Restore_Scripts](/customizations/scripts/backup-restore-scripts). Instead of keeping a local copy of the zip it will get uploaded to FTP. Locally in the backups folder you will see a zip with 0 bytes. This is used to remember which files have been uploaded.
9+
These scripts are a modified version of [Backup & Restore_Scripts](/customizations/scripts/general-scripts/backup-restore-scripts). Instead of keeping a local copy of the zip it will get uploaded to FTP. Locally in the backups folder you will see a zip with 0 bytes. This is used to remember which files have been uploaded.
1010
:::
1111

1212
## Secure your Backups folder
1313

14-
:::danger Urgent Warning: Critical Configuration Step - Neglect at Your Peril!
14+
:::warning Urgent Warning: Critical Configuration Step - Neglect at Your Peril!
1515
Failure to execute this pivotal step in the configuration process will render your server alarmingly susceptible to exploitations and security breaches.
1616
:::
1717

docs/customizations/scripts/backup-restore-scripts.mdx renamed to docs/customizations/scripts/general-scripts/backup-restore-scripts.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -7,7 +7,7 @@ sidebar_label: Backup & Restore Scripts
77

88
## Secure your Backups folder
99

10-
:::danger Urgent Warning: Critical Configuration Step - Neglect at Your Peril!
10+
:::warning Urgent Warning: Critical Configuration Step - Neglect at Your Peril!
1111
Failure to execute this pivotal step in the configuration process will render your server alarmingly susceptible to exploitations and security breaches.
1212
:::
1313

0 commit comments

Comments
 (0)