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: docs/products/tools/marketplace/guides/kepler/index.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -45,10 +45,10 @@ Kepler requires a valid license to use the software beyond the initial 14 day fr
45
45
-**Website Title:** Enter a title for your WordPress site.
46
46
47
47
{{< note >}}
48
-
The passwords for the WordPress Admin User, WordPress Database User and MySQL root user are automatically generated and provided in the file `/root/.credentials` when the WordPress deployment completes.
48
+
The passwords for the WordPress Admin User, WordPress Database User and MySQL root user are automatically generated and provided in the file `/root/.linode_credentials.txt` when the WordPress deployment completes.
@@ -76,7 +76,7 @@ Once the app has been *fully* deployed, you need to obtain the credentials from
76
76
1. Once logged in, access the credentials file by runing the following command:
77
77
78
78
```command
79
-
cat /root/.credentials
79
+
cat /root/.linode_credentials.txt
80
80
```
81
81
82
82
1. This displays the passwords that were automatically generated when the instance was deployed. Once you save these passwords, you can safely delete this file.
Copy file name to clipboardexpand all lines: docs/products/tools/marketplace/guides/lamp-stack/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -35,10 +35,10 @@ A LAMP (Linux, [Apache](https://www.apache.org), [MySQL](https://www.mysql.com),
35
35
-**Email address***(required)*: Enter the email address to use for generating the SSL certificates.
36
36
37
37
{{< note >}}
38
-
The password for the MySQL root user is automatically generated and provided in the file `/root/.credentials` when the LAMP deployment completes.
38
+
The password for the MySQL root user is automatically generated and provided in the file `/root/.linode_credentials.txt` when the LAMP deployment completes.
Copy file name to clipboardexpand all lines: docs/products/tools/marketplace/guides/lemp-stack/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -36,10 +36,10 @@ The LEMP stack (Linux, [NGINX](https://www.nginx.com/), [MySQL](https://www.mysq
36
36
-**Email address***(required)*: Enter the email address to use for generating the SSL certificates.
37
37
38
38
{{< note >}}
39
-
The password for the MySQL root user is automatically generated and provided in the file `/root/.credentials` when the LEMP deployment completes.
39
+
The password for the MySQL root user is automatically generated and provided in the file `/root/.linode_credentials.txt` when the LEMP deployment completes.
Copy file name to clipboardexpand all lines: docs/products/tools/marketplace/guides/mainconcept-live-encoder-demo/index.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -36,7 +36,7 @@ The version of MainConcept Live Encoder in this deployment is a free demo. It ad
36
36
37
37
-**Email address for SSL Generation (Required):** This is the contact email address used for communication regarding the SSL certificate created during deployment. This should be the email address of your web server administrator.
Copy file name to clipboardexpand all lines: docs/products/tools/marketplace/guides/secure-your-server/index.md
+6-6
Original file line number
Diff line number
Diff line change
@@ -28,19 +28,19 @@ This Marketplace App automatically configures a new Compute Instance with a limi
28
28
29
29
#### Limited User (Required)
30
30
31
-
You can fill out the following fields to automatically create a limited sudo user for your new Compute Instance. This account will be assigned to the *sudo* group, which provides elevated permission when running commands with the `sudo` prefix.
31
+
Fill out the following fields to automatically create a limited user for your new Compute Instance. This account will be assigned to the *sudo* group, which provides elevated permission when running commands with the `sudo` prefix.
32
32
33
-
-**Limited sudo user:** Enter your preferred username for the limited user. *No Capital Letters, Spaces, or Special Characters*
33
+
-**Limited sudo user:** Enter your preferred username for the limited user.
34
+
-**Password for the limited user:** Enter a *strong* password for the new user.
34
35
-**SSH public key for the limited user:** If you wish to login as the limited user through public key authentication (without entering a password), enter your public key here. See [Creating an SSH Key Pair and Configuring Public Key Authentication on a Server](/docs/guides/use-public-key-authentication-with-ssh/) for instructions on generating a key pair.
35
36
-**Disable root access over SSH:** To block the root user from logging in over SSH, select *Yes* (recommended). You can still switch to the root user once logged in and you can also log in as root through [Lish](/docs/products/compute/compute-instances/guides/lish/).
36
37
37
-
{{< note type="warning" title="Locating Your Sudo Password As Root">}}
38
-
If you disable root access for your deployment and do not enter a valid SSH public key, you will need to login as the root user via the [Lish console](/docs/products/compute/compute-instances/guides/lish/) and locate the credentials file found at `/root/.credentials` to obtain the limited sudo user password.
-**Email address:** The start of authority (SOA) email address for this server. This is a required field if you want the installer to create DNS records.
41
+
-**Send email from domain:** If you'd like to be able to send email from the custom domain you optionally configured, select **Yes**. This configures the related DNS records, allows traffic through relevant ports within the internal firewall, and sets the rDNS. It does not configure any email software or guarantee email deliverability.
Copy file name to clipboardexpand all lines: docs/products/tools/marketplace/guides/woocommerce/index.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -29,7 +29,7 @@ external_resources:
29
29
30
30
## Configuration Options
31
31
32
-
-**Supported distributions:**Ubuntu 22.04 LTS
32
+
-**Supported distributions:**Debian 10
33
33
-**Recommended minimum plan:** All plan types and sizes can be used, though a minimum of a 4GB Dedicated CPU Compute Instance is recommended for production websites.
34
34
35
35
### WooCommerce Options
@@ -42,10 +42,10 @@ external_resources:
42
42
-**Website Title:** Enter a title for your WordPress site.
43
43
44
44
{{< note >}}
45
-
The passwords for the WordPress Admin User, WordPress Database User and MySQL root user are automatically generated and provided in the file `/root/.credentials` when the WordPress deployment completes.
45
+
The passwords for the WordPress Admin User, WordPress Database User and MySQL root user are automatically generated and provided in the file `/root/.linode_credentials.txt` when the WordPress deployment completes.
-**Would you like to be able to send password reset emails for WordPress?** Creates the required DNS records and configures the server so you can send emails from WordPress, such as for resetting a password.
@@ -67,7 +67,7 @@ Once the app has been *fully* deployed, you need to obtain the credentials from
67
67
1. Once logged in, access the credentials file by runing the following command:
68
68
69
69
```command
70
-
cat /root/.credentials
70
+
cat /root/.linode_credentials.txt
71
71
```
72
72
73
73
1. This displays the passwords that were automatically generated when the instance was deployed. Once you save these passwords, you can safely delete this file.
Copy file name to clipboardexpand all lines: docs/products/tools/marketplace/guides/wordpress/index.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -43,7 +43,7 @@ authors: ["Linode"]
43
43
The passwords for the WordPress Admin User, WordPress Database User and MySQL root user are automatically generated and provided in the file `/root/.linode_credentials.txt` when the WordPress deployment completes.
@@ -63,7 +63,7 @@ Once the app has been *fully* deployed, you need to obtain the credentials from
63
63
1. Once logged in, access the credentials file by running the following command:
64
64
65
65
```command
66
-
cat /root/.credentials
66
+
cat /root/.linode_credentials.txt
67
67
```
68
68
69
69
1. This displays the passwords that were automatically generated when the instance was deployed. Once you save these passwords, you can safely delete this file.
0 commit comments