Merge pull request #2533 from Guaris/rc-v.0.15

[release] Rc v.0.15

ci/vale/dictionary.txt

@@ -17,6 +17,7 @@ ajp
 aker
 alives
 allmasquerade
+alphanumerics
 amavis
 amavisd
 amd64
@@ -543,6 +544,7 @@ icinga
 icingacli
 icmp
 icmpv6
+idempotence
 ident
 identrust
 idlist

docs/applications/configuration-management/install-a-chef-server-workstation-on-ubuntu-18-04/index.md

@@ -30,7 +30,7 @@ This guide is written for a non-root user. Commands that require elevated privil
   - Assign a Domain to the Chef server. Ensure your domain has a corresponding domain zone, NS record, and A/AAA record. See the [DNS Manager guide](/docs/platform/manager/dns-manager-new-manager/#add-a-domain-zone) for details.
   - Ensure your Chef server's hostname is the same as its Domain name. Your Chef server will automatically create SSL certificates based on the Linode's hostname.
 -  Two 2 GB Linodes, each running Ubuntu 18.04. One Linode will host a workstation and the other a node to be managed by Chef.
--  The workstation and Chef server should be configured per the [Getting Started](/docs/getting-started/) and [Securing Your Sever](/docs/security/securing-your-server/) guides. Once your node is [bootstrapped](/docs/applications/configuration-management/install-a-chef-server-workstation-on-ubuntu-18-04/#bootstrap-a-node), you can use a Chef cookbook to secure your node. Consider using the [Users](https://supermarket.chef.io/cookbooks/users) cookbook and the [Firewall](https://supermarket.chef.io/cookbooks/firewall) cookbook for this work.
+-  The workstation and Chef server should be configured per the [Getting Started](/docs/getting-started/) and [Securing Your Server](/docs/security/securing-your-server/) guides. Once your node is [bootstrapped](/docs/applications/configuration-management/install-a-chef-server-workstation-on-ubuntu-18-04/#bootstrap-a-node), you can use a Chef cookbook to secure your node. Consider using the [Users](https://supermarket.chef.io/cookbooks/users) cookbook and the [Firewall](https://supermarket.chef.io/cookbooks/firewall) cookbook for this work.
 -  Ensure that all servers are up-to-date:
 
         sudo apt update && sudo apt upgrade

docs/applications/containers/how-to-deploy-kubernetes-on-linode-with-rancher-2-2/completed-cluster-config.yml

@@ -8,8 +8,8 @@ addons: |-
     name: linode
     namespace: kube-system
   stringData:
-    token: "..."
-    region: "..."
+    token: “…”
+    region: “…”
   ---
 addon_job_timeout: 30
 authentication:
@@ -25,7 +25,7 @@ ignore_docker_version: true
 #
 ingress:
   provider: "nginx"
-kubernetes_version: "v1.13.4-rancher1-2"
+kubernetes_version: "v1.13.5-rancher1-3"
 monitoring:
   provider: "metrics-server"
 #
@@ -68,14 +68,15 @@ network:
 services:
   etcd:
     backup_config:
+      enabled: true
       interval_hours: 12
       retention: 6
     creation: "12h"
     extra_args:
       heartbeat-interval: 500
       election-timeout: 5000
     retention: "72h"
-    snapshot: true
+    snapshot: false
   kube-api:
     always_pull_images: false
     pod_security_policy: false
@@ -100,4 +101,4 @@ enable_cluster_monitoring: false
 enable_network_policy: false
 local_cluster_auth_endpoint:
   enabled: true
-name: "example-cluster"
+name: “example-cluster”

docs/applications/containers/how-to-deploy-kubernetes-on-linode-with-rancher-2-2/index.md

@@ -252,20 +252,9 @@ addons: |-
 
 1.  Insert your Linode APIv4 token in the `token` field from this snippet. Also, enter the label for your node template's data center in the `region` field. This label should be lower-case (e.g. `us-east` instead of `US-East`).
 
-1.  Scroll down in the editor to the `services` section. Remove the existing `services` section and replace it with this snippet:
+1.  Scroll down in the editor to the `services` section. Remove the `kube-api` sub-section and replace it with the example snippet. When editing the file, ensure you do not accidentally remove any other sections above or below the snippet.
 
     {{< file >}}
-services:
-  etcd:
-    backup_config:
-      interval_hours: 12
-      retention: 6
-    creation: "12h"
-    extra_args:
-      heartbeat-interval: 500
-      election-timeout: 5000
-    retention: "72h"
-    snapshot: true
   kube-api:
     always_pull_images: false
     pod_security_policy: false

docs/game-servers/multicraft-on-ubuntu/index.md

@@ -20,7 +20,7 @@ dedicated_cpu_link: true
 ![Installing Multicraft on Ubuntu](Installing_Multicraft_on_Ubuntu_smg.jpg)
 
 
-[Multicraft](http://www.multicraft.org/) is a control panel for single or multiple Minecraft servers, with free and paid versions available. This guide will help you install Multicraft on a Linode running Ubuntu 14.04.
+[Multicraft](http://www.multicraft.org/) is a control panel for single or multiple Minecraft servers, with free and paid versions available. This guide will help you install Multicraft on a Linode running Ubuntu 18.04 LTS.
 
 {{< note >}}
 The steps required in this guide require root privileges. Be sure to run the steps below as `root` or with the **sudo** prefix. For more information on privileges see our [Users and Groups](/docs/tools-reference/linux-users-and-groups/) guide.
@@ -32,13 +32,21 @@ Multicraft for Linux depends on several software packages in order to run.
 
 1.  Update your system:
 
-        apt-get update; apt-get upgrade -y
+        apt-get update && sudo apt-get upgrade
 
-2.  Install Apache2, SQLite, Java, PHP, and related packages:
+1.  Install Apache2 and SQLite:
 
-        apt-get install -y apache2 sqlite php5 php5-sqlite php5-gd openjdk-7-jre-headless
+        apt-get install apache2 sqlite
 
-3.  In Apache's configuration file, under the `<Directory /var/www/>` section, change the `AllowOverride` value to `all`.
+1.  Install PHP, SQLite, and related packages:
+
+        apt-get install php7.2 php7.2-sqlite php7.2-gd
+
+1.  Install Java:
+
+        apt-get install openjdk-8-jdk
+
+1.  In Apache's configuration file, under the `<Directory /var/www/>` section, change the `AllowOverride` value to `all`.
 
     {{< file "/etc/apache2/apache2.conf" apache >}}
 <Directory /var/www/>
@@ -88,40 +96,44 @@ Multicraft for Linux depends on several software packages in order to run.
 
 1.  In your local web browser, navigate to `http://12.34.56.78/multicraft/install.php`, replacing `12.34.56.78` with your Linode's IP address or domain name. Click on `Start Installation`:
 
-    [![Multicraft Installer.](multicraft-init_small.png)](multicraft-init.png)
+    [![Multicraft Installer.](multicraft-init_small-1804.png)](multicraft-init-1804.png)
 
 2.  Multicraft will check your requirements. If you completed the steps above without issue, your page should reflect the results show below:
 
-    [![Multicraft Requirements Check.](multicraft-reqs_small.png)](multicraft-reqs.png)
+    [![Multicraft Requirements Check.](multicraft-reqs_small-1804.png)](multicraft-reqs-1804.png)
 
     Click `Continue`.
 
 3.  Multicraft will attempt to copy the default `config.php` file into place. If successful, click `Continue`:
 
-    [![Multicraft Configuration File Transfer.](multicraft-config_small.png)](multicraft-config.png)
+    [![Multicraft Configuration File Transfer.](multicraft-config_small-1804.png)](multicraft-config-1804.png)
+
+4.  On the next page, click on `Initialize Database`.
 
-4.  On the next page, click on `Initialize Database`. Afterwards, click `Continue`:
+    [![Multicraft Database Initialization.](multicraft-db-initialize_small-1804.png)](multicraft-db-initialize-1804.png)
 
-    [![Multicraft Database Creation.](multicraft-db_small.png)](multicraft-db.png)
+5.  Afterwards, click `Continue`:
 
-5.  The next page will attempt to connect to the panel database. You should see the message `Connection successful`. You can now click on the `Login` button and sign in with the username and password `admin`.
+    [![Multicraft Database Creation.](multicraft-db_small-1804.png)](multicraft-db-1804.png)
 
-    [![Multicraft Panel Database Connection.](multicraft-panel_small.png)](multicraft-panel.png)
+6.  The next page will attempt to connect to the panel database. You should see the message `Connection successful`. You can now click on the `Login` button and sign in with the username and password `admin`.
 
-6.  After logging in you will be directed back to the previous page, where you can now click on `Continue`. The next page will allow you to configure your basic settings. When done, click `Save`.
+    [![Multicraft Panel Database Connection.](multicraft-panel_small-1804.png)](multicraft-panel-1804.png)
 
-7.  On the daemon configuration page, you will find a start command to initiate the Multicraft Daemon. Copy the command into your terminal:
+7.  After logging in you will be directed back to the previous page, where you can now click on `Continue`. The next page will allow you to configure your basic settings. When done, click `Save`.
+
+8.  On the daemon configuration page, you will find a start command to initiate the Multicraft Daemon. Copy the command into your terminal:
 
         /home/minecraft/multicraft/bin/multicraft -v start
-        Multicraft 1.8.2 - Minecraft Server Manager Daemon
+        Multicraft 2.3.1 - Minecraft Server Manager Daemon
         Loading configuration from /home/minecraft/multicraft/multicraft.conf
         Starting daemon
 
-8.  Back in your browser, click on `Refresh`. You should see the daemon in a green box. Click `Continue`:
+9.  Back in your browser, click on `Refresh`. You should see the daemon in the detected daemons list. Click `Continue`:
 
-    [![Multicraft Daemon Configuration.](multicraft-daemon_small.png)](multicraft-daemon.png)
+    [![Multicraft Daemon Configuration.](multicraft-daemon_small-1804.png)](multicraft-daemon-1804.png)
 
-9.  Your configuration of the Multicraft control panel is now complete. As per the instructions on the page, delete the `install.php` file from your terminal:
+10.  Your configuration of the Multicraft control panel is now complete. As per the instructions on the page, delete the `install.php` file from your terminal:
 
         rm /var/www/html/multicraft/install.php
 
@@ -131,30 +143,18 @@ Multicraft for Linux depends on several software packages in order to run.
 
         cd /home/minecraft/multicraft/jar/
 
-2.  Download the latest version of the Minecraft server (1.8.1 at the time of this publication) from the Minecraft [Download](https://minecraft.net/download) page:
-
-        wget https://s3.amazonaws.com/Minecraft.Download/versions/1.8.1/minecraft_server.1.8.1.jar
-
-3.  Back in the Multicraft web interface, click on `Servers`, then `Create Server`. Fill in the options as you see fit, but be sure to add `minecraft_server.1.8.1.jar` (or your downloaded version) in the `JAR File` field:
+1.  Download the latest version of the Minecraft server (1.14.2 at the time of this publication) from the Minecraft [Download](https://minecraft.net/download) page:
 
-    [![Multicraft Server Settings.](multicraft-server-settings_small.png)](multicraft-server-settings.png)
+        wget https://launcher.mojang.com/v1/objects/808be3869e2ca6b62378f9f4b33c946621620019/server.jar
 
-4.  The first time you attempt to start the Minecraft server it will fail. By checking the Console view, you should see the following output:
+1.  In your local web browser, navigate to `http://12.34.56.78/multicraft/`, replacing `12.34.56.78` with your Linode's IP address or domain name. Click on `Servers`.
 
-        ...
-        04.02 22:24:38 [Server] INFO [22:24:38] [Server thread/INFO]: Stopping server
-        04.02 22:24:38 [Server] INFO [22:24:38] [Server thread/INFO]: You need to agree to the EULA in order to run the server. Go to eula.txt for more info.
-        04.02 22:24:38 [Server] INFO [22:24:38] [Server thread/WARN]: Failed to load eula.txt
-        ...
+1.  At this time you must accept the Multicraft EULA. A pop-up window will appear. By clicking Close you are indicating your agreement to the EULA here: `http://www.multicraft.org/eula.txt`. Click Close.
 
-5.  After reading the End User License Agreement, open the file `eula.txt` in your terminal and change the value of `eula` to `true`:
+       [![Multicraft EULA.](multicraft-eula-popup.png)](multicraft-eula-popup.png)
 
-    {{< file "/home/minecraft/multicraft/servers/server1/eula.txt" aconf >}}
-#By changing the setting below to TRUE you are indicating your agreement to our EULA (https://account.mojang.com/documents/minecraft_eula).
-#Wed Feb 04 22:24:38 UTC 2015
-eula=true
-
-{{< /file >}}
+1.  Click `Create Server`. Fill in the options as you see fit, but be sure to add `server.jar` (or your downloaded version) in the `JAR File` field:
 
+    [![Multicraft Server Settings.](multicraft-server-settings_small-1804.png)](multicraft-server-settings-1804.png)
 
     You can now successfully start and manage your Minecraft server through Multicraft! For instructions on connecting to your Minecraft server, click [here](/docs/game-servers/how-to-set-up-minecraft-server-on-ubuntu-or-debian/#connect-to-your-minecraft-server).

docs/platform/manager/dns-manager/index.md

@@ -297,6 +297,10 @@ This generates a large amount of information about the domain. The basic informa
 
 For a web-based tool, you can also use [kloth.net](http://www.kloth.net/services/dig.php) for dig requests and [whois.net](http://whois.net/) for WHOIS requests. Note that since you're running these lookups from a third-party website, the information they find is not necessarily what your local computer has cached. There should be a difference only if you've made recent changes to your DNS information.
 
+## DNSSEC Limitations
+
+The Linode DNS Manager does not support DNSSEC at this time. If you have DNSSEC enabled at your domains registrar it will cause name resolution failures such as `NXDOMAIN` when an attempt is made to access the DNS.
+
 ## Next Steps
 
 Now that you are familiar with Linode's DNS Manager, you should set up your [reverse DNS configuration](/docs/networking/dns/configure-your-linode-for-reverse-dns/), and consider reading through at our [Common DNS Configurations](/docs/networking/dns/common-dns-configurations/) guide.

docs/platform/manager/using-the-linode-shell-lish/index.md

@@ -6,7 +6,7 @@ description: 'Learn how to use Lish as a shell for managing or rescuing your Lin
 keywords: ["Console", "Shell", "Lish", "rescue"]
 license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
 aliases: ['using-lish-the-linode-shell/','troubleshooting/using-lish-the-linode-shell/','networking/using-the-linode-shell-lish/','platform/using-the-linode-shell-lish/']
-modified: 2019-03-11
+modified: 2019-06-07
 modified_by:
   name: Linode
 published: 2009-08-04
@@ -263,8 +263,8 @@ These are the fingerprints for the Lish gateway in our Tokyo2 data center (lish-
 
 ### Toronto
 
-These are the fingerprints for the Lish gateway in our Tokyo2 data center (lish-tokyo2.linode.com):
+These are the fingerprints for the Lish gateway in our Toronto data center (lish-tor1.linode.com):
 
     RSA 4a:d9:fb:43:b8:0e:7f:fd:d3:cd:fc:87:06:61:51:df
     ECDSA SHA256:iAWnqR3XYcooliTQ7W1tiMmjsA4k1WJVItvLz4lUxQE
-    Ed25519 SHA256:TSbQmRFaaWEHKEwgwvqQFKMfHKduPftou9/ue9K/Z2c
+    Ed25519 SHA256:TSbQmRFaaWEHKEwgwvqQFKMfHKduPftou9/ue9K/Z2c

docs/platform/update-kernel/index.md

@@ -57,7 +57,7 @@ If your output contains `generic` in the version tag, then you are probably runn
 
 1.  Scroll to the *Boot Settings* section.
 
-1.  Select **Latest 64 bit** from the *Kernel* dropdown and click **Submit** to save the changes.
+1.  Select **Latest 64 bit** from the *Kernel* dropdown and click **Submit** to save the changes (if you need a 32-bit kernel, select **Latest 32 bit**).
 
 1.  Reboot the Linode to boot into the new kernel and verify the kernel version:
 

docs/quick-answers/websites/certbot-shortguide-centos/index.md

@@ -20,7 +20,7 @@ headless: true
 
 1.  Install the Certbot and web server-specific packages, then run Certbot:
 
-        sudo yum install python2-certbot-nginx
+        sudo yum install python2-certbot-nginx nginx
         sudo certbot --nginx
 
 1.  Certbot will ask for information about the site. The responses will be saved as part of the certificate:

docs/tools-reference/tools/modify-file-permissions-with-chmod/index.md

@@ -99,7 +99,7 @@ The `-R` option applies the modification to the permissions recursively to the d
 
 Another method for setting permissions is through octal notation.
 
-Here is example of a file permission that is equivalent to `chmod u=rwx,go=rx`.
+Here is example of a file permission that is equivalent to `chmod u=rwx,g=rx,o=`.
 
     chmod 750 ~/group-project.txt
 
@@ -122,7 +122,7 @@ Binary | Octal | Permission
   110  |   6   |   rw-
   111  |   7   |   rwx
 
-Each digit is independent of the other two. Therefore, `750` means the current user can read, write, and execute while the group and others cannot write.
+Each digit is independent of the other two. Therefore, `750` means the current user can read, write, and execute, the group cannot write, and others cannot read, write, or execute.
 
 `744`, which is a typical default permission, allows read, write, and execute permissions for the owner, and read permissions for the group and "world" users.
 

themes/docsmith/layouts/partials/includes_head_prod.html

@@ -1 +1 @@
-<link href="{{ relURL "build/stylesheets/home-2a488d70be.min.css" }}" rel='stylesheet' type='text/css'>
+<link href="{{ relURL "build/stylesheets/home-6541873c1f.min.css" }}" rel='stylesheet' type='text/css'>