From bebca48542916d42d597f35d8db6501e6c39a78e Mon Sep 17 00:00:00 2001 From: tanner0101 Date: Fri, 4 May 2018 21:37:51 -0400 Subject: [PATCH] deploy --- build/3.0/getting-started/hello-world/index.html | 6 +----- build/3.0/search/search_index.json | 8 ++++---- build/3.0/version/support/index.html | 13 ++++--------- 3 files changed, 9 insertions(+), 18 deletions(-) diff --git a/build/3.0/getting-started/hello-world/index.html b/build/3.0/getting-started/hello-world/index.html index ade91e68..29e1a105 100644 --- a/build/3.0/getting-started/hello-world/index.html +++ b/build/3.0/getting-started/hello-world/index.html @@ -2093,14 +2093,10 @@ This guide will take you step by step through creating a new project, building,

The first step is to create a new Vapor project on your computer. For this guide, we will call the project Hello.

Open up your terminal, and use Vapor Toolbox's new command.

-
vapor new Hello --branch=beta
+
vapor new Hello
 
-
-

Beta

-

At the time of this writing, Vapor 3 is not officially released. You can omit the --branch=beta flag once 3.0.0 is released.

-

Once that finishes, change into the newly created directory.

cd Hello
 
diff --git a/build/3.0/search/search_index.json b/build/3.0/search/search_index.json index 438f0130..0a13f5b9 100644 --- a/build/3.0/search/search_index.json +++ b/build/3.0/search/search_index.json @@ -137,7 +137,7 @@ }, { "location": "/getting-started/hello-world/", - "text": "Hello, world\n\n\nNow that you've installed Vapor, let's create your first Vapor app!\nThis guide will take you step by step through creating a new project, building, and running it.\n\n\nNew Project\n\n\nThe first step is to create a new Vapor project on your computer.\nFor this guide, we will call the project \nHello\n.\n\n\nOpen up your terminal, and use \nVapor Toolbox's \nnew\n command.\n\n\nvapor new Hello --branch\n=\nbeta\n\n\n\n\n\n\n\nBeta\n\n\nAt the time of this writing, Vapor 3 is not officially released. You can omit the \n--branch=beta\n flag once \n3.0.0\n is released.\n\n\n\n\nOnce that finishes, change into the newly created directory.\n\n\ncd\n Hello\n\n\n\n\n\nGenerate Xcode Project\n\n\nLet's now use the \nVapor Toolbox's \nxcode\n command to generate an Xcode project.\nThis will allow us to build and run our app from inside of Xcode, just like an iOS app.\n\n\nvapor xcode\n\n\n\n\n\nThe toolbox will ask you if you'd like to open Xcode automatically, select \nyes\n.\n\n\nBuild \n Run\n\n\nYou should now have Xcode open and running. Select the \nrun scheme\n from the scheme menu,\nthen click the play button.\n\n\nYou should see the terminal pop up at the bottom of the screen.\n\n\nServer starting on http://localhost:8080\n\n\n\n\n\nVisit Localhost\n\n\nOpen your web browser, and visit \nlocalhost:8080/hello \n\n\nYou should see the following page.\n\n\nHello, world!\n\n\n\n\n\nCongratulations on creating, building, and running your first Vapor app! \ud83c\udf89", + "text": "Hello, world\n\n\nNow that you've installed Vapor, let's create your first Vapor app!\nThis guide will take you step by step through creating a new project, building, and running it.\n\n\nNew Project\n\n\nThe first step is to create a new Vapor project on your computer.\nFor this guide, we will call the project \nHello\n.\n\n\nOpen up your terminal, and use \nVapor Toolbox's \nnew\n command.\n\n\nvapor new Hello\n\n\n\n\n\nOnce that finishes, change into the newly created directory.\n\n\ncd\n Hello\n\n\n\n\n\nGenerate Xcode Project\n\n\nLet's now use the \nVapor Toolbox's \nxcode\n command to generate an Xcode project.\nThis will allow us to build and run our app from inside of Xcode, just like an iOS app.\n\n\nvapor xcode\n\n\n\n\n\nThe toolbox will ask you if you'd like to open Xcode automatically, select \nyes\n.\n\n\nBuild \n Run\n\n\nYou should now have Xcode open and running. Select the \nrun scheme\n from the scheme menu,\nthen click the play button.\n\n\nYou should see the terminal pop up at the bottom of the screen.\n\n\nServer starting on http://localhost:8080\n\n\n\n\n\nVisit Localhost\n\n\nOpen your web browser, and visit \nlocalhost:8080/hello \n\n\nYou should see the following page.\n\n\nHello, world!\n\n\n\n\n\nCongratulations on creating, building, and running your first Vapor app! \ud83c\udf89", "title": "Hello, world" }, { @@ -147,7 +147,7 @@ }, { "location": "/getting-started/hello-world/#new-project", - "text": "The first step is to create a new Vapor project on your computer.\nFor this guide, we will call the project Hello . Open up your terminal, and use Vapor Toolbox's new command. vapor new Hello --branch = beta Beta At the time of this writing, Vapor 3 is not officially released. You can omit the --branch=beta flag once 3.0.0 is released. Once that finishes, change into the newly created directory. cd Hello", + "text": "The first step is to create a new Vapor project on your computer.\nFor this guide, we will call the project Hello . Open up your terminal, and use Vapor Toolbox's new command. vapor new Hello Once that finishes, change into the newly created directory. cd Hello", "title": "New Project" }, { @@ -2787,12 +2787,12 @@ }, { "location": "/version/support/", - "text": "Version Support\n\n\n\n\nVapor 3.0 is currently in beta.\n\n\nVapor 2.0 is currently active.\n\n\nVapor 1.5 is being maintained until November 2017.\n\n\n\n\nWarning\n\n\nDashed blocks and lines represent the team's goals and are not yet guaranteed. \nVapor 3's release and the beginning of Vapor 2's maintenance phase have not yet been decided.\n\n\n\n\nCore\n\n\nAll packages in the \nVapor GitHub\n are maintained according to the following rules.\n\n\nActive\n\n\nWhile a version is active, reported security issues and bugs are fixed.\n\n\nAdditionally, new features and optimizations may be added. If new API is added, the minor version number will be incremented. At no point can existing API be removed or broken during an active version. Semver is strictly followed and tested.\n\n\nMaintenance\n\n\nWhen a new version of Vapor is released, the previous version will enter a maintenance phase which lasts for six months. During this phase, critical security issues and bugs will be fixed. No new features will be added.\n\n\n\n\nNote\n\n\nOnly the latest minor version will be maintained.\n\n\n\n\nUnstable\n\n\nThe master branch is the latest development version of Vapor and is constantly changing. Before a new version of Vapor is released, there may be unstable alpha and beta phases in which you are welcome to test and provide feedback on the changes.\n\n\nCommunity\n\n\nAll packages in the \nVapor Community GitHub\n are maintained in strict accordance of semver. Violations of semver should be reported as issues to the offending package's GitHub page.", + "text": "Version Support\n\n\n\n\nVapor 3.0 is currently active.\n\n\nVapor 2.4 is being maintained until November 2018.\n\n\nVapor 1.5 is no longer maintained (ended November 2017).\n\n\nCore\n\n\nAll packages in the \nVapor GitHub\n are maintained according to the following rules.\n\n\nActive\n\n\nWhile a version is active, reported security issues and bugs are fixed.\n\n\nAdditionally, new features and optimizations may be added. If new API is added, the minor version number will be incremented. At no point can existing API be removed or broken during an active version. Semver is strictly followed and tested.\n\n\nMaintenance\n\n\nWhen a new version of Vapor is released, the previous version will enter a maintenance phase which lasts for six months. During this phase, critical security issues and bugs will be fixed. No new features will be added.\n\n\n\n\nNote\n\n\nOnly the latest minor version will be maintained.\n\n\n\n\nUnstable\n\n\nThe master branch is the latest development version of Vapor and is constantly changing. Before a new version of Vapor is released, there may be unstable alpha and beta phases in which you are welcome to test and provide feedback on the changes.\n\n\nCommunity\n\n\nAll packages in the \nVapor Community GitHub\n are maintained in strict accordance of semver. Violations of semver should be reported as issues to the offending package's GitHub page.", "title": "Support" }, { "location": "/version/support/#version-support", - "text": "Vapor 3.0 is currently in beta. Vapor 2.0 is currently active. Vapor 1.5 is being maintained until November 2017. Warning Dashed blocks and lines represent the team's goals and are not yet guaranteed. \nVapor 3's release and the beginning of Vapor 2's maintenance phase have not yet been decided.", + "text": "Vapor 3.0 is currently active. Vapor 2.4 is being maintained until November 2018. Vapor 1.5 is no longer maintained (ended November 2017).", "title": "Version Support" }, { diff --git a/build/3.0/version/support/index.html b/build/3.0/version/support/index.html index d266878e..78c026fe 100644 --- a/build/3.0/version/support/index.html +++ b/build/3.0/version/support/index.html @@ -2113,15 +2113,10 @@

Version Support

-

Support Matrix

-

Vapor 3.0 is currently in beta.

-

Vapor 2.0 is currently active.

-

Vapor 1.5 is being maintained until November 2017.

-
-

Warning

-

Dashed blocks and lines represent the team's goals and are not yet guaranteed. -Vapor 3's release and the beginning of Vapor 2's maintenance phase have not yet been decided.

-
+

Support Matrix

+

Vapor 3.0 is currently active.

+

Vapor 2.4 is being maintained until November 2018.

+

Vapor 1.5 is no longer maintained (ended November 2017).

Core

All packages in the Vapor GitHub are maintained according to the following rules.

Active