Update Limits Page (#1459)

* update limits page

* add remaining limits, fix prettier config

* clarify http2/push

* Apply suggestions from code review

Co-Authored-By: Timothy <[email protected]>

* correct limits

* add link to pricing

Author: Matthew Sweeney

.prettierignore

@@ -1,4 +1,3 @@
 .next
 dist
 lib/data/last-edited.json
-pages/examples

.prettierrc.js

@@ -0,0 +1,5 @@
+{
+  "semi": false,
+  "singleQuote": true,
+  "tabWidth": 2
+}

.prettierrc.json

@@ -0,0 +1,16 @@
+const Infinity = () => (
+  <svg
+    viewBox="0 0 24 24"
+    width="24"
+    height="24"
+    stroke="currentColor"
+    stroke-width="1.5"
+    stroke-linecap="round"
+    stroke-linejoin="round"
+    fill="none"
+    shape-rendering="geometricPrecision"
+  >
+    <path d="M13.833 8.875S15.085 7 18.043 7C21 7 23 9.5 23 12s-1.784 5-4.864 5-4.914-3.124-6.136-5c-1.222-1.875-3.392-5-6.446-5S1 9.5 1 12s1.351 5 4.648 5c3.296 0 4.519-1.875 4.519-1.875" />
+  </svg>
+)
+export default Infinity

components/icons/infinity.js

@@ -3,41 +3,75 @@ import Limits from '~/components/limits'
 
 export const meta = {
   title: 'Limits',
-  description: 'A list of rate limits that apply on the ZEIT Now platform.',
+  description:
+    'A list of limits and limitations that apply on the ZEIT Now platform.',
   editUrl: 'pages/docs/v2/platform/limits.mdx',
-  lastEdited: '2019-10-30T09:43:23.000Z'
+  lastEdited: '2019-11-12T19:50:43.000Z'
 }
 
-This page outlines all relevant limits on the ZEIT Now platform.
+This page outlines all relevant limits and limitations present when using the ZEIT Now platform.
 
-The table consists of the following four columns:
+## Plans
 
-- **Description** - A brief description of the limit which, where relevant, will advise what type of plan it applies to.
-- **Limit** - The amount of actions permitted within the amount of time (**Duration**) specified.
-- **Duration** - The amount of time (seconds) in which you can perform the specified amount of actions in. Once a rate limit is hit, it will be reset after the **Duration** has expired.
-- **Scope** - Who the limit applies to, `owner` refers to the account owner, `user` refers to an individual user on a **Team** account.
+This section highlights two areas relating to pricing plans, **Usage Allowances**, and **Plan Limits**.
 
-## Examples
+### Usage Allowances
 
-Below are three examples that provide further information on how the rate limits work.
+**Usage Allowances** are the maximum limits provided by each pricing plan. They specify a limit for the amount of resources available for use under that plan before deployments are blocked (Free plan) or [additional costs](/pricing) are incurred.
 
-### Domain Deletion
+| Limit                  | Free | Pro | Business | Enterprise |
+| ---------------------- | ---- | --- | -------- | ---------- |
+| Bandwidth (GB)         | 20   | 100 | 1000     | Custom     |
+| Build Time (Hours)     | 2    | 10  | 100      | Custom     |
+| Execution Time (Hours) | 20   | 100 | 1,000    | Custom     |
+| Team Seats             | 3    | 3   | 6        | Custom     |
+| Concurrent Builds      | 1    | 3   | 6        | Custom     |
 
-Taking the domains deletion rate limit as an example, you are allowed to delete up to `60` domains every `60` seconds (1 minute). Should you hit the rate limit, you will need to wait another minute before deleting another domain.
+### Plan Limits
 
-### Team Deletion
+**Plan Limits** are limitations that apply to specific plans that **cannot** be increased, the only way to do so is to upgrade to a higher tier pricing plan.
 
-With the team deletion rate limit, you are able to delete up to `20` teams every `3600` seconds (1 hour). Should you hit the rate limit, you will need to wait another hour before deleting another team.
+| Limit                        | Free | Pro  | Business | Enterprise |
+| ---------------------------- | ---- | ---- | -------- | ---------- |
+| Deployments (per day)        | 100  | 3000 | 3000     | Custom     |
+| Deployment History           | 10   | -    | -        | -          |
+| Execution Duration (Seconds) | 10   | 60   | 600      | 900        |
 
-### Username Update
+## Logs
 
-For the username update rate limit, you are able to change your username up to `6` times every `604800` seconds (1 week). Should you hit the rate limit, you will need to wait another week before changing your username again.
+Both log types – **build time** and **runtime** – are stored for **20 days only**. It is not possible to retrieve either of these log types beyond the age of 20 days.
 
----
+For [Serverless Functions](/docs/v2/serverless-functions/introduction/), each log output is **limited to 4kb**. For log outputs greater than 4kb, only the last 4kb will be retained.
 
-<Limits />
+## Environment Variables
 
----
+The total size of [environment variables](/docs/v2/serverless-functions/env-and-secrets/) is **limited to 4kb**.
+
+[Deployments](/docs/v2/platform/deployments) made with environment variables exceeding the 4kb limit will fail at the [build step](/docs/v2/build-step/).
+
+## Domains
+
+The maximum amount of domains that can be applied to a single project, either from the ZEIT Dashboard or by using the `alias` key in a `now.json` file is **50**.
+
+It is not possible to add more than 50 domains to a project using the ZEIT Dashboard.
+
+[Deployments](/docs/v2/platform/deployments) made with more than 50 `alias` in a `now.json` file will fail at the [build step](/docs/v2/build-step/).
+
+## Files
+
+The maximum number of files that can be uploaded when making a [deployment](/docs/v2/platform/deployments) is **10,000**.
+
+Deployments made that contain more than 10,000 files will fail at the [build step](/docs/v2/build-step/).
+
+## HTTP/2 Push
+
+The ZEIT Now platform does not currently support HTTP/2 Push.
+
+## SMTP
+
+For security reasons, the ZEIT Now platform blocks outgoing SMTP connections.
+
+As a result of this, we recommend using a third-party service to enable email functionality for [deployments](/docs/v2/platform/deployments).
 
 ## Reserved Variables
 
@@ -61,7 +95,38 @@ The following environment variable names are [reserved](https://docs.aws.amazon.
 - `LAMBDA_TASK_ROOT`
 - `LAMBDA_RUNTIME_DIR`
 
-Using any of these environment variable names will result in the deployment failing.
+[Deployments](/docs/v2/platform/deployments) made that use any of the reserved variable names will fail at the [build step](/docs/v2/build-step/).
+
+## Rate Limits
+
+**Rate limits** are hard limits that apply to the platform when performing actions that require a response from an API.
+
+The **rate limits** table consists of the following four columns:
+
+- **Description** - A brief summary of the limit which, where relevant, will advise what type of plan it applies to.
+- **Limit** - The amount of actions permitted within the amount of time (**Duration**) specified.
+- **Duration** - The amount of time (seconds) in which you can perform the specified amount of actions. Once a rate limit is hit, it will be reset after the **Duration** has expired.
+- **Scope** - Who the limit applies to, `owner` refers to the account owner, `user` refers to an individual user on a **Team** account.
+
+## Examples
+
+Below are three examples that provide further information on how the rate limits work.
+
+### Domain Deletion
+
+Taking the domains deletion rate limit as an example, you are allowed to delete up to `60` domains every `60` seconds (1 minute). Should you hit the rate limit, you will need to wait another minute before deleting another domain.
+
+### Team Deletion
+
+With the team deletion rate limit, you are able to delete up to `20` teams every `3600` seconds (1 hour). Should you hit the rate limit, you will need to wait another hour before deleting another team.
+
+### Username Update
+
+For the username update rate limit, you are able to change your username up to `6` times every `604800` seconds (1 week). Should you hit the rate limit, you will need to wait another week before changing your username again.
+
+---
+
+<Limits />
 
 export default ({ children }) => <Doc meta={meta}>{children}</Doc>