Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Release] v1.360.0 #7180

Merged
merged 6 commits into from
Jan 28, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion _vendor/modules.txt
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
# github.com/linode/linode-docs-theme v0.0.0-20250110174948-7f99bcdf9fa2
# github.com/linode/linode-docs-theme v0.0.0-20250124183022-1528603da313
# github.com/linode/linode-website-partials v0.0.0-20250103220935-91c22c1d82ec
# github.com/gohugoio/hugo-mod-jslibs-dist/alpinejs/v3 v3.21300.20800
# github.com/gohugoio/hugo-mod-jslibs/turbo/v8 v8.20000.20400
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -198,15 +198,15 @@ ModSecurity is a firewall and therefore requires rules to function. This section
1. Copy over the unicode mapping file and the ModSecurity configuration file from your cloned ModSecurity GitHub repository:

sudo cp /opt/ModSecurity/unicode.mapping /etc/nginx/modsec
sudo cp /opt/ModSecurity/modsecurity.conf-recommended /etc/nginx/modsec/modsecurity.conf
sudo cp /opt/ModSecurity/modsecurity.conf-recommended /etc/nginx/modsec

1. Remove the `.recommended` extension from the ModSecurity configuration filename with the following command:
1. Remove the `-recommended` extension from the ModSecurity configuration filename with the following command:

sudo cp /etc/modsecurity/modsecurity.conf-recommended /etc/modsecurity/modsecurity.conf
sudo cp /etc/nginx/modsec/modsecurity.conf-recommended /etc/nginx/modsec/modsecurity.conf

1. With a text editor such as vim, open `/etc/modsecurity/modsecurity.conf` and change the value for `SecRuleEngine` to `On`:
1. With a text editor such as vim, open `/etc/nginx/modsec/modsecurity.conf` and change the value for `SecRuleEngine` to `On`:

{{< file "/etc/modsecurity/modsecurity.conf" aconf >}}
{{< file "/etc/nginx/modsec/modsecurity.conf" aconf >}}
# -- Rule engine initialization ----------------------------------------------

# Enable ModSecurity, attaching it to every transaction. Use detection
Expand Down
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.

Large diffs are not rendered by default.

51 changes: 30 additions & 21 deletions docs/marketplace-docs/guides/drupal/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,35 +29,49 @@ In addition to the core infrastructure, there are a number of freely available D

## Configuration Options

- **Supported distributions:** Ubuntu 22.04 LTS
- **Supported distributions:** Ubuntu 24.04 LTS
- **Recommended minimum plan:** All plan types and sizes can be used.

### Drupal Options

- **Database Root Password** *(required)*: Password for your Drupal site's MariaDB database `root` user.
- **Database User Password** *(required)*: Password for your Drupal site's MariaDB database `drupal` user.
- **Email address** *(required)*: Email address to use for generating the SSL certificates.
- **Drupal Site Name** *(required)*: Drupal site name.
- **Drupal Site Email** *(required)*: Drupal site email for system notifications.
- **Drupal Account Email** *(required)*: Drupal account email address for an admin user.
- **Drupal User Name** *(required)*: Admin username for the Drupal site.

{{% content "marketplace-required-limited-user-fields-shortguide" %}}

{{% content "marketplace-custom-domain-fields-shortguide" %}}

{{% content "marketplace-special-character-limitations-shortguide" %}}

## Getting Started after Deployment
### Obtain the Credentials

### Access your Drupal Site
Once the app is deployed, you need to obtain the credentials from the server.

1. Open a web browser and navigate to the domain you entered when creating the instance: `https://domain.tld`. If you did not enter a domain, use your Compute Instance's default rDNS domain (`192-0-2-1.ip.linodeusercontent.com`). See the [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide for information on viewing the rDNS value. Ensure that you are securely accessing the website by prefixing `https` to the URL.
To obtain the credentials:

1. The initial configuration and installation screen for your Drupal site should be displayed. Follow the prompts for the **Choose language**, **Choose profile**, and **Verify requirements** screens, selecting the appropriate configuration values for your Drupal site.
1. Log in to your new Compute Instance using one of the methods below:

![Screenshot of the Drupal installation screen](drupal-install.png)
- **Lish Console**: Log in to Cloud Manager, click the **Linodes** link in the left menu, and select the Compute Instance you just deployed. Click **Launch LISH Console**. Log in as the `root` user. To learn more, see [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/).
- **SSH**: Log in to your Compute Instance over SSH using the `root` user. To learn how, see [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/).

1. In the **Database configuration** screen, fill in the form with the values listed below. Click on **Save and Continue** when you are done.
1. Run the following command to access the credentials file:

- **Database name:** `drupaldb`
- **Database username:** `drupal`
- **Database password:** Enter the database user password you created when deploying the instance.
```command
cat /home/$USERNAME/.credentials
```

1. Continue to follow the prompts for the **Configure site** screen and select the appropriate configuration values for your Drupal site. When complete, you are brought to your Drupal site's admin panel where you can begin [building your Drupal site](https://www.drupal.org/documentation/build).
This returns passwords that were automatically generated when the instance was deployed. Save them. Once saved, you can safely delete the file.

![Screenshot of the Drupal admin panel](drupal-admin.png)
## Getting Started after Deployment

### Access your Drupal Site

To access your Drupal site:

1. Open a web browser and navigate to the domain you entered when creating the instance: `https://domain.tld`. If you didn't provide a domain, use your Compute Instance's default rDNS domain (`192-0-2-1.ip.linodeusercontent.com`). To learn more on viewing the rDNS value, see [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make sure to use the `https` prefix in the URL to access the website securely.

## Software Included

Expand All @@ -66,13 +80,8 @@ The Drupal Marketplace App installs the following required software on your Lino
| **Software** | **Description** |
|:--------------|:------------|
| [**MariaDB Server**](https://mariadb.org/) | Relational database. |
| [**PHP 8**](https://www.php.net) | Drupal is written in PHP and requires PHP to operate. |
| [**PHP**](https://www.php.net) | Drupal is written in PHP and requires PHP to operate. |
| [**Apache HTTP Server**](https://httpd.apache.org) | Web Server used to serve the Drupal site. |
| [**Drupal 10**](https://www.drupal.org/about/10) | Content management system. |
| [**Drupal**](https://www.drupal.org/) | Content management system. |

{{% content "marketplace-update-note-shortguide" %}}

## Next Steps

- Register a domain name and [create a DNS record](/docs/products/networking/dns-manager/) for it using the Linode Cloud Manager.
- [Configure your Apache HTTP Server](/docs/guides/how-to-install-a-lamp-stack-on-debian-10/#configure-name-based-virtual-hosts) to point to your domain name.
2 changes: 1 addition & 1 deletion docs/marketplace-docs/guides/lamp-stack/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,7 +27,7 @@ A LAMP (Linux, [Apache](https://www.apache.org), [MySQL](https://www.mysql.com),

## Configuration Options

- **Supported distributions:** Ubuntu 22.04 LTS
- **Supported distributions:** Ubuntu 24.04 LTS
- **Recommended minimum plan:** 1GB Shared Compute Instance or higher, depending on the number of sites and size of the sites you plan on hosting.

### LAMP Stack Options
Expand Down
2 changes: 1 addition & 1 deletion docs/marketplace-docs/guides/lemp-stack/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@ The LEMP stack (Linux, [NGINX](https://www.nginx.com/), [MySQL](https://www.mysq

## Configuration Options

- **Supported distributions:** Ubuntu 22.04 LTS
- **Supported distributions:** Ubuntu 24.04 LTS
- **Recommended minimum plan:** 1GB Shared Compute Instance or higher, depending on the number of sites and size of the sites you plan on hosting.

### LEMP Stack Options
Expand Down
44 changes: 35 additions & 9 deletions docs/marketplace-docs/guides/rabbitmq/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,30 +29,56 @@ The RabbitMQ Marketplace App installs a RabbitMQ server and a basic default conf

## Configuration Options

- **Supported distributions:** Debian 10
- **Supported distributions:** Ubuntu 24.04 LTS
- **Recommended minimum plan:** All plan types and sizes can be used.

### RabbitMQ Options

- **RabbitMQ Username** *(required)*: The username for accessing the rabbitMQ management console.
- **RabbitMQ Password** *(required)*: The user password for SSH access to the Linode.
- **Email address** *(required)*: Email address to use for generating the SSL certificates and configuring the server and DNS records.
- **Allowed IPs** *(required)*: IP addresses allowed to access the Management UI.
- **The version of RabbitMQ you'd like installed** *(required)*: RabbitMQ version to be installed during the setup.
- **RabbitMQ Admin Username** *(required)*: RabbitMQ admin username.
- **RabbitMQ Username** *(required)*: RabbitMQ limited AMQP user. Make sure to use a username different from the **RabbitMQ Admin Username**.

{{% content "marketplace-required-limited-user-fields-shortguide" %}}

{{% content "marketplace-custom-domain-fields-shortguide" %}}

{{% content "marketplace-special-character-limitations-shortguide" %}}

## Getting Started After Deployment
### Obtain the Credentials

Once the app is deployed, you need to obtain the credentials from the server.

To obtain credentials:

1. Log in to your new Compute Instance using one of the methods below:

- **Lish Console**: Log in to Cloud Manager, click the **Linodes** link in the left menu, and select the Compute Instance you just deployed. Click **Launch LISH Console**. Log in as the `root` user. To learn more, see [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/).
- **SSH**: Log in to your Compute Instance over SSH using the `root` user. To learn how, see [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/).

1. Open your web browser and navigate to the following URL, replacing *[ip-address]* with your Compute Instance's IPv4 address or default rDNS domain. See the [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide for information on viewing IP addresses.
1. Run the following command to access the credentials file:

```command
http://[ip-address]:15672
cat /home/$USERNAME/.credentials
```

1. In the login form that appears, enter the username and password you created during the deployment. Then, click the **Login** button.
This returns passwords that were automatically generated when the instance was deployed. Save them. Once saved, you can safely delete the file.

## Getting Started After Deployment

To get started:

1. Open a web browser and navigate to the domain you entered when creating the instance: `https://domain.tld`. If you didn't enter a domain, use your Compute Instance's default rDNS domain (`192-0-2-1.ip.linodeusercontent.com`). To learn more on viewing the rDNS value, see [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make sure to use the `https` prefix in the URL to access the website securely.

1. Log in with your username and password found in your /home/$USERNAME/.credentials file.

![Screenshot of the RabbitMQ Login page](rabbitmq-login.png)

1. After you login successfully, you have full access to the RabbitMQ Management Console. From you, you can start configuring your application. To learn more about using RabbitMQ, visit the official [RabbitMQ Tutorials](https://www.rabbitmq.com/getstarted.html) page.
Now, you have full access to the RabbitMQ Management Console and you can start configuring your application.

![Screenshot of the RabbitMQ Management Console](rabbitmq-dashboard.png)

![Screenshot of the RabbitMQ Management Console](rabbitmq-dashboard.png)
To learn more on RabbitMQ, see [RabbitMQ Tutorials](https://www.rabbitmq.com/getstarted.html).

{{% content "marketplace-update-note-shortguide" %}}
30 changes: 20 additions & 10 deletions docs/marketplace-docs/guides/uptime-kuma/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -27,35 +27,45 @@ license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'

## Configuration Options

- **Supported distributions:** Ubuntu 22.04 LTS
- **Supported distributions:** Ubuntu 24.04 LTS
- **Recommended plan:** All plan types and sizes can be used.

### Uptime Kuma Options

- **Email address** *(required)*: Enter the email address to use for generating the SSL certificates.
- **Uptime-Kuma Username** *(required)*: Enter the username to login to your Uptime-Kuma instance.

{{% content "marketplace-required-limited-user-fields-shortguide" %}}

{{% content "marketplace-custom-domain-fields-shortguide" %}}

{{% content "marketplace-special-character-limitations-shortguide" %}}

## Getting Started after Deployment
### Obtain the Credentials

### Accessing the Uptime Kuma App
Once the app is deployed, you need to obtain the credentials from the server.

1. Open your web browser and navigate to `https://DOMAIN/`, where *DOMAIN* can be replaced with the custom domain you entered during deployment or your Compute Instance's rDNS domain (such as `192-0-2-1.ip.linodeusercontent.com`). See the [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/) guide for information on viewing rDNS.
To obtain credentials:

![Screenshot of URL bar](uptimekuma-url.png)
1. Log in to your new Compute Instance using one of the methods below:

1. If this is your first time logging in, the account creation page appears. Complete the form and click the **Create** button.
- **Lish Console**: Log in to Cloud Manager, click the **Linodes** link in the left menu, and select the Compute Instance you just deployed. Click **Launch LISH Console**. Log in as the `root` user. To learn more, see [Using the Lish Console](/docs/products/compute/compute-instances/guides/lish/).
- **SSH**: Log in to your Compute Instance over SSH using the `root` user. To learn how, see [Connecting to a Remote Server Over SSH](/docs/guides/connect-to-server-over-ssh/).

![Screenshot of account creation form](uptimekuma-create-user.png)
1. Run the following command to access the credentials file:

1. After creating a user, you are automatically logged in and the Uptime Kuma dashboard is displayed.
```command
cat /home/$USERNAME/.credentials
```

![Screenshot of Uptime Kuma dashboard](uptimekuma-dashboard.png)
This returns passwords that were automatically generated when the instance was deployed. Save them. Once saved, you can safely delete the file.

Now that you’ve accessed your dashboard, check out [the official Uptime Kuma Repository](https://github.com/louislam/uptime-kuma) to learn how to further use your Uptime Kuma instance.
## Getting Started After Deployment

To get started:

1. Open a web browser and navigate to the domain you entered when creating the instance: `https://domain.tld`. If you didn't enter a domain, use your Compute Instance's default rDNS domain (`192-0-2-1.ip.linodeusercontent.com`). To learn more on viewing the rDNS value, see [Managing IP Addresses](/docs/products/compute/compute-instances/guides/manage-ip-addresses/). Make sure to use the `https` prefix in the URL to access the website securely.

1. Check [the official Uptime Kuma Repository](https://github.com/louislam/uptime-kuma) to learn how you can use your Uptime Kuma instance.

{{% content "marketplace-update-note-shortguide" %}}
Loading