Skip to content

Commit 328060b

Browse files
authored
Merge pull request #201 from HOSTED-POWER/BjarneVO-KBrestructure
Bjarne vo k brestructure
2 parents 0efd572 + fc737dc commit 328060b

11 files changed

Lines changed: 30 additions & 30 deletions

File tree

TurboStack Platform/Hosts/Accounts/accountclone.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ icon: upload
55

66
# Cloning an account
77

8-
To make a clone of an **existing application**, we provide the **Clone Account** feature. This function **replicates the entire configuration** and **copies the files and database**, enabling a quick and efficient setup with minimal effort.
8+
To make a **clone of an existing application**, we provide the **Clone Account** feature. This function **replicates the entire configuration** and optionally **copies the files and/or database**, enabling a quick and efficient setup with minimal effort.
99

1010
!!!Info
1111
This feature is extremely useful to quickly copy your production environment to a staging environment or vice versa!

TurboStack Platform/Hosts/Accounts/databaseusers.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ label: Extra database users
66

77
## Adding extra database users
88

9-
It is possible to add an **additional database user** with **read-only** or **admin** access to a databases. You can also retrieve the **credentials** for this user.
9+
It is possible to add an **additional database user** with **read-only** or **admin** access to a database. You can also retrieve the **credentials** for this user.
1010
![](../../../img/turbostackapp/newapp/tsa_extra_db_user1.png)
1111
![](../../../img/turbostackapp/newapp/tsa_extra_db_user2.png)
1212
**admin**: Full access to ALL server databases.

TurboStack Platform/Hosts/Accounts/migrationhero.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -9,9 +9,9 @@ label: Migration Hero
99
To simplify the migration of your external application to TurboStack, the **Migration Hero** feature is available. It automatically transfers the full configuration, files and database. Enabling a fast and efficient setup with minimal effort.
1010

1111
!!! info
12-
If you want to migrate an application from TurboStack to TurboStack, please use the **Account Cloning** feature documented below.
12+
If you want to migrate an application from TurboStack to TurboStack, please use the [Account Cloning](accountclone.md) feature.
1313
!!!
14-
14+
[accountclone.md](accountclone.md)
1515
Before starting, make sure you have already **created an application** and successfully performed a **Save and Publish**.
1616

1717
1. Navigate to the **Accounts** tab in the TurboStack Platform under your host.
@@ -21,7 +21,7 @@ Before starting, make sure you have already **created an application** and succe
2121
![](../../../img/turbostackapp/newapp/tsa_migration_hero1.png)
2222

2323
3. In the next step, enter the **remote host** and the **user** you want to migrate.
24-
Then, choose the authentication method you want to use to connect to the remote host.
24+
Then, choose the **authentication method** you want to use to connect to the remote host.
2525
![](../../../img/turbostackapp/newapp/tsa_migration_hero2.png)
2626

2727
4. **Option 1:** Enter the password for the user on the remote host, then click **Next**.
@@ -36,5 +36,5 @@ Then, choose the authentication method you want to use to connect to the remote
3636
7. Select the **hostname(s)** you want to associate with the account and choose the **type of certificate** to generate. Click **Start Import** to begin the migration.
3737
![](../../../img/turbostackapp/newapp/tsa_migration_hero6.png)
3838

39-
8. A migration progress popup will appear in the bottom-right corner. Once it finishes, your migration is complete.
39+
8. A migration progress popup will appear in the bottom-right corner. Once it finishes, your migration is complete!
4040
![](../../../img/turbostackapp/newapp/tsa_migration_hero7.png)

TurboStack Platform/Hosts/Accounts/setup.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ New servers can also be autoconfigured using **Templates**! Visit [this](../../t
1212

1313
## What is an account and what is it used for?
1414

15-
The account is a **Linux user** which can be used simply to access the server. However, you probably want to deploy one or multiple **applications** under this user. This guide will explain how to deploy system users and all settings your application requires.
15+
The account is a **Linux user** which can be used simply to access the server. However, you probably want to deploy **one or multiple applications** under this user. This guide will explain how to deploy system users and all settings your application requires.
1616

1717
!!!
1818
For staging and production instances of an application, best practice is always to use an entirely different server, because it's by design unavoidable that resources allocated for staging, will be (silently) "taken away" from production. Even when this staging application is rarely used, it would still consume memory for e.g. databases, causing avoidable overhead.
@@ -22,9 +22,7 @@ For staging and production instances of an application, best practice is always
2222

2323
### Deploying a new account in the GUI
2424

25-
Creating a new user on the [TurboStack Platform](https://my.turbostack.app "TurboStack Platform").
26-
27-
* Open the TurboStack Platform
25+
* Open the [TurboStack Platform](https://my.turbostack.app "TurboStack Platform")
2826
* Open the server management console in the **Hosts** section
2927

3028
1. Go to the **Accounts** page
@@ -60,7 +58,7 @@ Creating a new (default) application under the newly created **prod** user.
6058
![](../../../img/turbostackapp/newapp/tsa_app2.png)
6159
3. The first application for each user should always be **default**.
6260
![](../../../img/turbostackapp/newapp/tsa_app3.png)
63-
4. Fill in 1 or more **hostnames** your application will listen on.
61+
4. Fill in **1 or more hostnames** your application will listen on.
6462
![](../../../img/turbostackapp/newapp/tsa_appX.png)
6563
5. Choose an **SSL certificate**, there are 3 options: **letsencrypt**(default), **self-signed** and **custom** (3rd party certificate).
6664
@@ -87,12 +85,14 @@ The **app type** should match the CMS or framework that will be installed on thi
8785
8886
Please note that two more publishing options are available:
8987
90-
- **Save & Full Publish**: Redeploy the whole server configuration as opposed to only the changes
88+
- **Save & Full Publish**: Redeploy the **whole server configuration** as opposed to only the changes
9189
- **Save, Delete & Full Publish**: Same as **Save & Full Publish**, but is required when **explicitly deleting** certain configs. You will be prompted to verify this option by typing 'DELETE' as a failsafe.
9290
9391
![](../../../img/turbostackapp/newapp/tsa_app10.png)
9492
93+
!!! info
9594
Depending on the volume and impact of changes, publishing can take some time! When the publication of your TurboStack has completed successfully, a message indicating so with a timestamp will appear in the top right corner:
95+
!!!
9696
9797
![Successful publication](../../../img/turbostackapp/newapp/publishsuccess.png)
9898

TurboStack Platform/Hosts/advancedtab.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -19,19 +19,19 @@ The **advanced** tab offers some more advanced configuration options for specifi
1919
2. Choose a **selector** for the DKIM record. This selector will be used as the **subdomain** part of the record.
2020
3. SSH to the server and use the command `tscli dkim records` to **acquire your DKIM record**.
2121
4. **Create the DKIM record** in your domain's DNS settings
22-
5. SSH to the server and use the command `tscli dkim validate` to check if the **DNS record was created correctly**.
22+
5. SSH to the server and use the command `tscli dkim validate` to **check if the DNS record was created correctly**.
2323
6. All done!
2424

2525
!!! info
26-
DKIM is part of your domain's mail **deliverability** optimisation. For more information on mail deliverability, take a look [here](../../Configuration/Mail/deliverability.md).
26+
DKIM is part of your domain's **mail deliverability** optimisation. For more information on mail deliverability, take a look [here](../../Configuration/Mail/deliverability.md).
2727
!!!
2828

2929
### Mail Devtool - Enabling mail capturing and mail testing
3030

31-
TurboStack allows you to use either **Mailpit** or **Mailhog** to test your mailing. Once activated, you can reach the GUI through the URLs https://<hostname>/mailpit or https://<hostname>/mailhog respectively. Here, a basic auth prompt will appear, where you can enter the [system user's credentials](Accounts/credentials.md).
31+
TurboStack allows you to use either **Mailpit** or **Mailhog** to test your mailing. Once activated, you can reach the GUI through the URLs `https://<hostname>/mailpit` or `https://<hostname>/mailhog` respectively. Here, a **basic auth prompt** will appear, where you can enter the [system user's credentials](Accounts/credentials.md).
3232

3333
!!! info
34-
We currently recommend Mailpit over Mailhog, as the Mailhog project is no longer receiving updates.
34+
We currently recommend Mailpit over Mailhog, as the Mailhog project is no longer receiving updates!
3535
!!!
3636

3737
## Varnish Options
@@ -40,11 +40,11 @@ We currently recommend Mailpit over Mailhog, as the Mailhog project is no longer
4040

4141
### Varnish Cache Size
4242

43-
This value determines the **amount of memory** that can be used by Varnish to store cached content. The default setting **auto-scales** based on your server flavour, but can be set to a size of your preference.
43+
This value determines the **amount of memory** that can be used by Varnish to **store cached content**. The default setting **auto-scales** based on your server flavour, but can be set to a size of your preference.
4444

4545
### Use your own Varnish custom VCL
4646

47-
Your Varnish is set up to use a **default VCL** (Varnish Configuration Language) based on and optimised for your selected **app type**. However, you can use your own VCL if you wish. To do so, toggle this option on and add your VCL file to the directory `/etc/varnish/conf.d/` on your server.
47+
Your Varnish is set up to use a **default VCL** (Varnish Configuration Language) based on and optimised for your selected **app type**. However, you can use **your own VCL** if you wish. To do so, toggle this option on and add your VCL file to the directory `/etc/varnish/conf.d/` on your server.
4848

4949
### Varnish Flavor
5050

@@ -64,19 +64,19 @@ The RabbitMQ Plugins options allows you to easily **install RabbitMQ plugins**.
6464

6565
### Enable Valid Certificate For FTP Server
6666

67-
Generate an SSL certificate for FTP connections using a hostname of your choice. This hostname must point to the server IP in order to work!
67+
**Generate an SSL certificate** for FTP connections using a **ostname of your choice**. This hostname must point to the server IP in order to work!
6868

6969
### Enable SFTP for FTP Users
7070

71-
Enables SFTP connections over **port 222** using the existing FTP daemon and users. This does not work over port 22, as this is reserved for the SSH service.
71+
**Enables SFTP connections** over **port 222** using the existing FTP daemon and users. This does not work over port 22, as this is reserved for the SSH service.
7272

7373
## Operating System
7474

7575
![Operating System](img/advancedtaboperatingsystem.png)
7676

7777
### OS Extra Packages
7878

79-
A non-exhaustive list of packages to install. Please note this list is not complete, and more options are available when using source YAML mode! More info on editing YAML can be found [here](yaml.md)
79+
A non-exhaustive **list of packages** available for **automated installation**. Please note this list is not complete, and more options are available when using source YAML mode! More info on editing YAML can be found [here](yaml.md)
8080

8181
### Maintenance Window
8282

TurboStack Platform/Hosts/groupstab.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,4 +9,4 @@ Groups make it possible to **apply certain settings across multiple TurboStack n
99

1010
![Groups Tab](img/groupstab.png)
1111

12-
This section of the **Hosts** management allows you to apply or remove Groups you have created separately to and from the current server. More info on what Groups are and how to manage them can be found [here](../groups.md).
12+
This section of the **Hosts** management allows you to **apply or remove Groups** you have created separately to and from the current server. More info on what **Groups** are and how to manage them can be found [here](../groups.md).

TurboStack Platform/Hosts/monitoring.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,7 +15,7 @@ The general health of the server can be seen in the TurboStack Platform overview
1515
3. CPU load and usage
1616
4. Disk usage
1717

18-
If any of these checks alert, the icons will become red. When this is the case, please contact the [Hosted Power Support](../../Support/standard_support.md) asap.
18+
If any of these checks alert, the icons will become red. When this is the case, please contact our [Support](../../Support/standard_support.md) ASAP.
1919

2020
## Website monitoring URL
2121

TurboStack Platform/Hosts/securitytab.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ icon: lock
88
This is an advanced feature, please be cautious while changing values here!
99
!!!
1010

11-
The **Security** tab allows you to modify certain firewall settings.
11+
The **Security** tab allows you to **modify certain firewall settings**.
1212

1313
## Whitelist IP Addresses
1414

TurboStack Platform/Hosts/servertab.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ The **server** tab defines some basic middleware configuration, like the type of
99

1010
## Webserver
1111

12-
We offer both **nginx** and **Apache2** as web server options. For **optimal performance** and **efficiency**, Nginx is our default choice, though Apache2 remains fully compatible and performs reliably on our TurboStack.
12+
We offer both **nginx and Apache2** as web server options. For **optimal performance** and **efficiency**, nginx is our default choice, though Apache2 remains fully compatible and performs reliably on our TurboStack.
1313

1414
![Webserver settings](img/servertabwebserver.png)
1515

TurboStack Platform/Hosts/sshtab.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This tab allows you to add your **SSH public key** to the server, enabling keypa
1111

1212
We recommend toggling the option **Only allow SSH authentication by keys** on when all SSH keys have been added. This provides **extra security**, even when your system user credentials have been compromised!
1313

14-
Need help creating your SSH key, or need help deploying your key(s) on cPanel or Directadmin? Have a look [here](../../Miscellaneous/ssh.md)!
14+
Need help with **creating your SSH key**, or **deploying your key(s) on cPanel or Directadmin**? Have a look [here](../../Miscellaneous/ssh.md)!
1515

1616
!!! info
1717
If deploying multiple SSH keys, please consider using [Groups](../groups.md)! This allows centralised access management over all servers, eliminating the need to control access on your servers separately.

0 commit comments

Comments
 (0)