[Release Candidate] v0.10

ci/vale/dictionary.txt

@@ -87,6 +87,7 @@ bashrc
 bc
 berkshelf
 binlog
+biomes
 bitbucket
 bitrate
 blocklists
@@ -371,6 +372,7 @@ fediverse
 fetchmail
 fetchmailrc
 ff02
+fi
 fiiiile
 file1
 filebeat
@@ -406,6 +408,7 @@ fstab
 galera
 gamemode
 gamepad
+gamepedia
 gameplay
 gandi
 gatsby
@@ -476,6 +479,7 @@ h4x0r123
 hackage
 hadoop
 halls3
+hapis
 haproxy
 hardcoded
 hardcopy
@@ -652,6 +656,7 @@ kubernetes
 kubespray
 lambdabunker
 laravel
+largebiomes
 launchd
 lbmethod
 lda
@@ -764,6 +769,7 @@ microservices
 microsystems
 microweb
 minecraft
+mineshafts
 miniconda
 miniconda3
 minification
@@ -778,6 +784,7 @@ mitigations
 mkdir
 mnesia
 moby
+moddable
 modsecurity
 mongodb
 monit
@@ -1083,6 +1090,7 @@ resharding
 resilvering
 resolv
 resolvconf
+respawn
 resque
 restapi
 retpoline
@@ -1134,6 +1142,7 @@ sasl2
 saslauth
 saslauthd
 sasldb
+savas
 sbackup
 sbin
 sbopkg
@@ -1353,7 +1362,9 @@ tw
 txt
 txz
 ucd
+udp
 ufw
+udp
 ui
 uidl
 umount

docs/platform/billing-and-support/billing-and-payments/index.md

@@ -180,7 +180,6 @@ You can cancel your account and receive a refund. Here's how:
 1.  Log in to the [Classic Linode Manager](http://manager.linode.com).
 1.  Click the **Accounts** link.
 1.  At the bottom of the page, select the **Cancel this Account** link. The cancel account webpage appears.
-1.  If you have a prepaid service credit on your account at the time of cancellation, you are entitled to a refund, minus a $5 processing fee. To request a refund, enter a note in the text field. Note that credits from sources other than prepaying cannot be refunded.
 1.  Select the confirmation checkbox.
 1.  Click the **Cancel this Account Immediately** checkbox.
 
@@ -189,7 +188,3 @@ Your account will be canceled and all of your services will be deactivated.
 {{< note >}}
 You do not have to cancel your account to prevent recurring charges. Instead, you can remove all Linodes and services from your account via the **Linodes** tab in the Cloud Manager. This will allow you to retain your Linode account. If you use Longview with non-Linode services, or want to keep your account name and history, you may find this to be a useful option. See the [Removing Services](#removing-services) section for more information.
 {{< /note >}}
-
-## Prepaid Billing
-
-If you created your account before hourly billing was first available and have not converted to hourly billing, your account uses prepaid billing. Review the legacy [Prepaid Billing](/docs/platform/billing-and-support/prepaid-billing-and-payments-legacy/) guide for more information on how your bills and invoices are prepared.

docs/platform/billing-and-support/upgrade-to-hourly-billing/index.md

@@ -11,6 +11,7 @@ modified_by:
   name: Linode
 published: 2017-02-15
 title: 'Upgrade to Hourly Billing'
+deprecated: true
 ---
 
 This guide will show you how to upgrade your legacy prepaid billing Linode account to use Hourly billing. For more information on Hourly billing, see our [Billing Guide](/docs/platform/billing-and-support/billing-and-payments/).
@@ -51,4 +52,4 @@ You will no longer receive the annual discount when you switch to Hourly billing
 
 [![Please note the annual discounts will go away when converting to Hourly.](convert-to-hourly-annual-small.png)](convert-to-hourly-annual.png)
 
-On March 31st all prepaid accounts will be automatically converted to to Hourly billing. 
+On March 31st, 2019 all prepaid accounts will be automatically converted to to Hourly billing.

docs/platform/one-click/_index.md

@@ -0,0 +1,11 @@
+---
+author:
+  name: Linode
+  email: docs@linode.com
+description: 'Use One-Click Apps to easily deploy a Linode with pre-installed software, like WordPress, Minecraft, and OpenVPN.'
+keywords: ['one-click', 'apps']
+license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+published: 2019-03-26
+title: One-Click Apps
+show_in_lists: true
+---

docs/platform/one-click/deploy-gitlab-with-one-click-apps/index.md

@@ -0,0 +1,126 @@
+---
+author:
+  name: Linode Community
+  email: docs@linode.com
+description: 'Deploy GitLab on Linode using One-Click Apps.'
+keywords: ['gitlab','one-click apps','version control','git']
+license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+published: 2019-03-27
+modified: 2019-03-27
+modified_by:
+  name: Linode
+title: "Deploy GitLab with One-Click Apps"
+contributor:
+  name: Linode
+external_resources:
+- '[GitLab Adminstrator Documentation](https://docs.gitlab.com/ee/administration/)'
+---
+## GitLab One-Click App
+
+GitLab is a complete solution for all aspects of your software development. At its core, GitLab serves as your centralized remote Git repository. GitLab also features built-in tools that represent every task in your development workflow, from planning to testing to releasing.
+
+Self-hosting your software development with GitLab offers total control of your codebase. At the same time, its familiar interface will ease collaboration for you and your team. GitLab is the most popular self-hosted Git repository software, so you'll benefit from a robust set of integrated tools and an active community.
+
+### Deploy a GitLab One-Click App
+
+{{< content "deploy-one-click-apps">}}
+
+### GitLab Options
+
+You can configure your GitLab App by providing values for the following fields:
+
+| **Field** | **Description** |
+|:--------------|:------------|
+| **Domain** | Your GitLab site's domain name. This domain will also be used by Postfix to send mail. Setting a value for this field will not automatically set up DNS for your app, so be sure to follow the DNS instructions in the [Access your GitLab Site](#access-your-gitlab-site) section. If you do not have a domain name, you can leave this field blank and Postfix will use your Linode's default Reverse DNS to send email instead (i.e. `gitlab@li926-227.members.linode.com`).  *Advanced Configuration*. |
+| **SSH public key** | Your SSH [public key](/docs/security/authentication/use-public-key-authentication-with-ssh/). The public key will be stored in the `/root/.ssh/authorized_keys` file on your Linode. *Advanced Configuration*. |
+
+### Linode Options
+
+After providing the app specific options, provide configurations for your Linode server:
+
+| **Configuration** | **Description**&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; |
+|--------------|------------|
+| **Select an Image** | Debian 9 is currently the only image supported by the GitLab One-Click App, and it is pre-selected on the Linode creation page. *Required*. |
+| **Region** | The region where you would like your Linode to reside. In general, it's best to choose a location that's closest to you. For more information on choosing a DC, review the [How to Choose a Data Center](/docs/platform/how-to-choose-a-data-center) guide. You can also generate [MTR reports](/docs/networking/diagnostics/diagnosing-network-issues-with-mtr/) for a deeper look at the network routes between you and each of our data centers. *Required*. |
+| **Linode Plan** | Your Linode's [hardware resources](/docs/platform/how-to-choose-a-linode-plan/#hardware-resource-definitions). We recommend that you use, at minimum, an **8GB Linode plan** for your GitLab server. For more information on GitLab's system requirements see their [official documentation](https://docs.gitlab.com/ee/install/requirements.html). If you decide that you need more or fewer hardware resources after you deploy your app, you can always [resize your Linode](/docs/platform/disk-images/resizing-a-linode/) to a different plan. *Required*. |
+| **Linode Label** | The name for your Linode, which must be unique between all of the Linodes on your account. This name will be how you identify your server in the Cloud Manager’s Dashboard. *Required*. |
+| **Root Password** | The primary administrative password for your Linode instance. This password must be provided when you log in to your Linode via SSH. It must be at least 6 characters long and contain characters from two of the following categories: lowercase and uppercase case letters, numbers, and punctuation characters. Your root password can be used to perform any action on your server, so make it long, complex, and unique. *Required*. |
+
+When you've provided all required Linode Options, click on the **Create** button. **Your GitLab app will complete installation anywhere between 3-7 minutes after your Linode has finished provisioning**.
+
+## Getting Started after Deployment
+
+### Access your GitLab Site
+
+After GitLab has finished installing, you will be able to access your GitLab site over `http://` with your Linode's IPv4 address or the domain name entered when deploying your GitLab One-Click App.
+
+1. Access your GitLab instance:
+
+    **With your Linode's IP Address**
+
+    You will be able to access your GitLab site by copying your Linode's IPv4 address and entering it in the browser of your choice. To find your Linode's IPv4 address:
+
+    1. Click on the **Linodes** link in the sidebar. You will see a list of all your Linodes.
+
+    1. Find the Linode you just created when deploying your app and select it.
+
+    1. Navigate to the **Networking** tab.
+
+    1. Your IPv4 address will be listed under the **Address** column in the **IPv4** table.
+
+    1. Copy and paste the IPv4 address into a browser window. Ensure you are using `http://`.
+
+    **With a Domain Name**
+
+    If you deployed your GitLab One-Click App with a value set for the **Domain** field, you will need to separately set up DNS for your app. Specifically, you'll need to create an [*A record*](/docs/networking/dns/dns-records-an-introduction/#a-and-aaaa) associated with the IPv4 address for your Linode. Review the [DNS Manager](/docs/platform/manager/dns-manager/) guide for instructions on setting up DNS records.
+
+    Once your DNS records are created (and the changes have [propagated to your internet service provider](/docs/platform/manager/dns-manager/#wait-for-propagation)), you can then enter the domain name in a browser window to access your GitLab site. Ensure you are using `http://` when visiting your site.
+
+    {{< note >}}
+For more general information about how DNS works, review the [DNS Records: An Introduction](/docs/networking/dns/dns-records-an-introduction/) guide.
+{{< /note >}}
+
+1. Once you have accessed your GitLab site, you will be brought to GitLab's password reset screen. Provide a secure password for the administrator's account:
+
+    ![Create a password for the adminstrator's account.](gitlab-reset-password.png)
+
+1. You will be redirected to the login screen. Enter `root` as the username and the password you just created to log in. You can now begin creating GitLab repositories, users, and more. See [GitLab's official documentation](https://docs.gitlab.com/ee/university/training/topics/getting_started.html) for more information.
+
+### Add a Domain after Deploying your GitLab Instance
+
+If you configured your GitLab One-Click App without providing a domain, you can configure one after the app has been deployed. Begin by setting up DNS for your domain:
+
+1.  Create an [*A record*](/docs/networking/dns/dns-records-an-introduction/#a-and-aaaa) associated with the IPv4 address for your Linode. Review the [DNS Manager](/docs/platform/manager/dns-manager/) guide for instructions on setting up DNS records.
+
+1.  Wait for your new DNS records to [propagate to your internet service provider](/docs/platform/manager/dns-manager/#wait-for-propagation).
+
+After setting up DNS, you will need to update your GitLab instance's `/etc/gitlab/gitlab.rb` file with your domain name. This will ensure that any emails sent to users by the GitLab instance will use your site's domain.
+
+1.  [Connect to your Linode via SSH](/docs/getting-started/#connect-to-your-linode-via-ssh).
+
+1.  With a text editor of your choice ([nano](/docs/quick-answers/linux/use-nano-to-edit-files-in-linux/), for example), open the `/etc/gitlab/gitlab.rb` file and modify the value of `external_url`. Ensure you replace `http://example.com` with your domain:
+
+    {{< file "/etc/gitlab/gitlab.rb" >}}
+## GitLab URL
+##! URL on which GitLab will be reachable.
+##! For more details on configuring external_url see:
+##! https://docs.gitlab.com/omnibus/settings/configuration.html#configuring-the-external-url-for-gitlab
+external_url 'http://example.com'
+{{< /file >}}
+
+1.  Issue the following command to enable your new configuration:
+
+        gitlab-ctl reconfigure
+
+1.  Navigate to the domain in a browser window and verify that you are directed to your GitLab instance.
+
+### Software Included
+
+The GitLab One-Click App will install the following required software on your Linode:
+
+| **Software** | **Description** |
+|:--------------|:------------|
+| [**GitLab**](https://about.gitlab.com/) | Remote Git repository software. |
+| [**Postfix**](http://www.postfix.org/) | Postfix is a free and open-source mail transfer agent that routes and delivers electronic mail. |
+| [**UFW**](https://wiki.ubuntu.com/UncomplicatedFirewall) | Firewall utility. Ports 22/tcp, 80/tcp, 443/tcp, 25, 587, and 110 for IPv4 and IPv6 will allow outgoing and incoming traffic. |
+| [**Fail2ban**](https://www.fail2ban.org/wiki/index.php/Main_Page) | Fail2Ban is an intrusion prevention software framework that protects computer servers from brute-force attacks. |

docs/platform/one-click/deploy-lamp-stack-with-one-click-apps/index.md

@@ -0,0 +1,76 @@
+---
+author:
+  name: Linode Community
+  email: docs@linode.com
+description: 'Use One-Click Apps to deploy a LAMP stack on Linode'
+keywords: ['LAMP', 'apache', 'web server', 'mysql', 'php']
+license: '[CC BY-ND 4.0](https://creativecommons.org/licenses/by-nd/4.0)'
+published: 2019-03-26
+modified: 2019-03-26
+modified_by:
+  name: Linode
+title: "Deploy a LAMP Stack with One-Click Apps"
+contributor:
+  name: Linode
+external_resources:
+- '[Apache Getting Started](http://httpd.apache.org/docs/current/getting-started.html)'
+---
+
+## LAMP Stack One-Click App
+
+A LAMP (Linux, [Apache](https://www.apache.org), [MySQL](https://www.mysql.com), [PHP](https://www.php.net)) stack is a popular, free, and open-source web software bundle used for hosting websites on Linux. This software environment is a foundation for popular PHP application frameworks like WordPress, Drupal, and Laravel. After you deploy your LAMP One-Click App, you can upload your existing PHP application code to it or use a PHP framework to write a new application on your Linode.
+
+### Deploy a LAMP Stack with One-Click Apps
+
+{{< content "deploy-one-click-apps" >}}
+
+The [LAMP Stack Options](#lamp-stack-options) section of this guide provides details on all available configuration options for this app.
+
+### LAMP Stack Options
+
+| **Field** | **Description** |
+|:--------------|:------------|
+| **MySQL Root Password** | The root password for your LAMP stack's MySQL database. This is not the same as your Linode's root password. *Required*. |
+
+### Linode Options
+
+After providing the app-specific options, enter configuration values for your Linode server:
+
+| **Configuration** | **Description** |
+|:--------------|:------------|
+| **Select an Image** | Debian 9 is currently the only image supported by the LAMP One-Click App, and it is pre-selected on the Linode creation page. *Required*. |
+| **Region** | The region where you would like your Linode to reside. In general, it's best to choose a location that's closest to you. For more information on choosing a DC, review the [How to Choose a Data Center](/docs/platform/how-to-choose-a-data-center) guide. You can also generate [MTR reports](/docs/networking/diagnostics/diagnosing-network-issues-with-mtr/) for a deeper look at the network routes between you and each of our data centers. *Required*. |
+| **Linode Plan** | Your Linode's [hardware resources](/docs/platform/how-to-choose-a-linode-plan/#hardware-resource-definitions). The Linode plan you deploy your LAMP stack on should account for the estimated workload. If you are standing up a simple web page, you can use a Nanode or 2GB Linode. If you are standing up a larger or more robust web app, then consider a plan with higher RAM and CPU allocations. If you decide that you need more or fewer hardware resources after you deploy your app, you can always [resize your Linode](/docs/platform/disk-images/resizing-a-linode/) to a different plan. *Required*. |
+| **Linode Label** | The name for your Linode, which must be unique between all of the Linodes on your account. This name will be how you identify your server in the Cloud Manager’s Dashboard. *Required*. |
+| **Root Password** | The primary administrative password for your Linode instance. This password must be provided when you log in to your Linode via SSH. It must be at least 6 characters long and contain characters from two of the following categories: lowercase and uppercase case letters, numbers, and punctuation characters. Your root password can be used to perform any action on your server, so make it long, complex, and unique. *Required*. |
+
+When you've provided all required Linode Options, click on the **Create** button. **Your LAMP Stack app will complete installation anywhere between 2-3 minutes after your Linode has finished provisioning.**
+
+### Getting Started After Deployment
+
+After your LAMP stack has finished deploying, you can:
+
+- [Connect to your Linode via SSH](/docs/getting-started/#connect-to-your-linode-via-ssh). You will need your Linode's root password to proceed. Note that your Linode's web root will be located in the `/var/www/html` directory.
+
+- [Navigate to the public IP address](/docs/getting-started/#find-your-linode-s-ip-address) of your Linode in a browser. You will see the PHP settings that are active for your Linode.
+
+- Consult the following guides to learn more about working with the various components of the LAMP stack:
+
+    - [Secure HTTP Traffic with Certbot](https://linode.com/docs/quick-answers/websites/secure-http-traffic-certbot/)
+    - [Apache Configuration Basics](/docs/web-servers/apache-tips-and-tricks/apache-configuration-basics/)
+    - [How to Optimize MySQL Performance Using MySQLTuner](/docs/databases/mysql/how-to-optimize-mysql-performance-using-mysqltuner/)
+
+-   Upload files to your web root directory with an SFTP application like [FileZilla](/docs/tools-reference/file-transfer/filezilla/). Use the same root credentials that you would use for SSH.
+
+-   Assign a domain name to your Linode's IP address. Review the [DNS Manager](/docs/platform/manager/dns-manager/) guide for instructions on setting up your DNS records in the Cloud Manager, and read through [DNS Records: An Introduction](/docs/networking/dns/dns-records-an-introduction/) for general information about how DNS works.
+
+### Software Included
+
+The LAMP Stack One-Click App will install the following software on your Linode:
+
+| **Software** | **Description** |
+|:--------------|:------------|
+| [**Apache HTTP Server**](https://www.apache.org) | Web server that can be used to serve your site or web application.|
+| [**MySQL Server**](https://www.mysql.com) | Relational database. |
+| [**PHP 7**](https://www.php.net) | General purpose programming language. |
+| [**UFW (Uncomplicated Firewall)**](https://en.wikipedia.org/wiki/Uncomplicated_Firewall) | Firewall utility. Ports 22/tcp, 80/tcp, and 443/tcp for IPv4 and IPv6 will allow outgoing and incoming traffic. |