You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/Accounts/accountclone.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -5,7 +5,7 @@ icon: upload
5
5
6
6
# Cloning an account
7
7
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.
9
9
10
10
!!!Info
11
11
This feature is extremely useful to quickly copy your production environment to a staging environment or vice versa!
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/Accounts/databaseusers.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -6,7 +6,7 @@ label: Extra database users
6
6
7
7
## Adding extra database users
8
8
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.
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/Accounts/migrationhero.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,9 +9,9 @@ label: Migration Hero
9
9
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.
10
10
11
11
!!! 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.
13
13
!!!
14
-
14
+
[accountclone.md](accountclone.md)
15
15
Before starting, make sure you have already **created an application** and successfully performed a **Save and Publish**.
16
16
17
17
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
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
36
36
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.
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/Accounts/setup.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,7 +12,7 @@ New servers can also be autoconfigured using **Templates**! Visit [this](../../t
12
12
13
13
## What is an account and what is it used for?
14
14
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.
16
16
17
17
!!!
18
18
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
22
22
23
23
### Deploying a new account in the GUI
24
24
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")
28
26
* Open the server management console in the **Hosts** section
29
27
30
28
1. Go to the **Accounts** page
@@ -60,7 +58,7 @@ Creating a new (default) application under the newly created **prod** user.
5. Choose an **SSL certificate**, there are 3 options: **letsencrypt**(default), **self-signed** and **custom** (3rd party certificate).
66
64
@@ -87,12 +85,14 @@ The **app type** should match the CMS or framework that will be installed on thi
87
85
88
86
Please note that two more publishing options are available:
89
87
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
91
89
- **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.
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:
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/advancedtab.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,19 +19,19 @@ The **advanced** tab offers some more advanced configuration options for specifi
19
19
2. Choose a **selector** for the DKIM record. This selector will be used as the **subdomain** part of the record.
20
20
3. SSH to the server and use the command `tscli dkim records` to **acquire your DKIM record**.
21
21
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**.
23
23
6. All done!
24
24
25
25
!!! 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).
27
27
!!!
28
28
29
29
### Mail Devtool - Enabling mail capturing and mail testing
30
30
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).
32
32
33
33
!!! 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!
35
35
!!!
36
36
37
37
## Varnish Options
@@ -40,11 +40,11 @@ We currently recommend Mailpit over Mailhog, as the Mailhog project is no longer
40
40
41
41
### Varnish Cache Size
42
42
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.
44
44
45
45
### Use your own Varnish custom VCL
46
46
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.
48
48
49
49
### Varnish Flavor
50
50
@@ -64,19 +64,19 @@ The RabbitMQ Plugins options allows you to easily **install RabbitMQ plugins**.
64
64
65
65
### Enable Valid Certificate For FTP Server
66
66
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!
68
68
69
69
### Enable SFTP for FTP Users
70
70
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.
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)
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/groupstab.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,4 +9,4 @@ Groups make it possible to **apply certain settings across multiple TurboStack n
9
9
10
10

11
11
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).
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/monitoring.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -15,7 +15,7 @@ The general health of the server can be seen in the TurboStack Platform overview
15
15
3. CPU load and usage
16
16
4. Disk usage
17
17
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.
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/servertab.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -9,7 +9,7 @@ The **server** tab defines some basic middleware configuration, like the type of
9
9
10
10
## Webserver
11
11
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.
Copy file name to clipboardExpand all lines: TurboStack Platform/Hosts/sshtab.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -11,7 +11,7 @@ This tab allows you to add your **SSH public key** to the server, enabling keypa
11
11
12
12
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!
13
13
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)!
15
15
16
16
!!! info
17
17
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