Merge pull request fly-apps#1 from rugwirobaker/update-docs

Docs use flyctl launch

Author: jsierles

Diff for: README.md

@@ -73,79 +73,86 @@ We are ready to start working with Fly and that means we need `flyctl`, our CLI
 
 ## _Configure the App for Fly_
 
-Each Fly application needs a `fly.toml` file to tell the system how we'd like to deploy it. That file can be automatically generated with the command `flyctl init` command. We are going to use one of Fly's builtin deployment configurations for python
+Each Fly application needs a `fly.toml` file to tell the system how we'd like to deploy it. That file can be automatically generated with the command `flyctl launch` command. We are going to use one of Fly's builtin deployment configurations for Python.
 
 ```cmd
-flyctl init
+flyctl launch
 ```
 ```output
-? App Name (leave blank to use an auto-generated name) hellofly-python
-
-? Select organization: demo (demo)
-
-? Select builder: python
-    Python builtin
-Builtins use port 8080
-New app created
-  Name         = hellofly-python
-  Organization = personal
-  Version      = 0
-  Status       =
-  Hostname     = <empty>
-
-App will initially deploy to lhr (London, United Kingdom) region
-
+Creating app in /<path>/python-hellofly-flask
+Scanning source code
+Detected a Python app
+Using the following build configuration:
+        Builder: paketobuildpacks/builder:base
+Selected App Name: 
+? Select region: lhr (London, United Kingdom)
+Created app hellofly-flask in organization personal
 Wrote config file fly.toml
+We have generated a simple Procfile for you. Modify it to fit your needs and run "fly deploy" to deploy your application.
 ```
 
 You'll be asked for an application name first. We recommend that you go with the autogenerated names for apps to avoid namespace collisions. We're using `hellofly-python` here so you can easily spot it in configuration files.
 
-Next you'll be prompted for an organization. Organizations are a way of sharing applications between Fly users. When you are asked to select an organization, there should be one with your account name; this is your personal organization. Select that.
+Next you'll be prompted for an organization. Organizations allow sharing applications between Fly users. When you are asked to select an organization, there should be one with your account name; this is your personal organization. Select that.
 
-Flyctl also asks you to select a builder. Builders are responsible for constructing the Docker image of your application which is then deployed to Fly's Firecracker VMs. The simplest to use are the builtin builders, which we recommend you use here. Select Python (Python Builtin). If you want to know more about the various builders, see [_Builders and Fly_](/docs/reference/builders/).
+Now `flyctl launch` will generate a sample `Procfile` and `fly.toml`, which together will define how fly deploys and launches the application.
 
-One thing to know about the builtin Python builder is that it will automatically copy over the contents of the  directory to the deployable image. This is how you can move static assets such as templates and other files to your application. The other thing to know is that it uses a Procfile to run the application; Procfiles are used on other platforms to deploy Python applications so we keep it simple. The Procfile contains instructions for starting the application. Here's the contents of ours:
+Update the `Procfile` to look like this:
 
 ```Procfile
 web: gunicorn hellofly:app
 ```
 
-This says the web component of the application is served by `gunicorn` (which we mentioned earlier when talking about dependencies) and that should run the hellofly Flask app as we set up for Flask.
+This says the web component of the application is served by `gunicorn` (which we mentioned earlier when talking about dependencies) and that it should run the `hellofly` Flask app.
 
 ## _Inside `fly.toml`_
 
-The `fly.toml` file now contains a default configuration for deploying your app. In the process of creating that file, `flyctl` has also created a Fly-side application slot of the same name, `hellofly`. If we look at the `fly.toml` file we can see the name in there:
+The `fly.toml` file now contains a default configuration for deploying your app. In the process of creating that file, `flyctl` has also created a Fly-side application slot of the same name, `hellofly-python`. If we look at the `fly.toml` file we can see the name in there:
 
 ```toml
-# fly.toml file generated for hellofly-python on 2021-01-13T15:21:15Z
+# fly.toml file generated for hellofly-python on 2021-11-30T17:37:33+02:00
 
 app = "hellofly-python"
 
-[build]
-  builtin = "python"
-
 kill_signal = "SIGINT"
 kill_timeout = 5
+processes = []
+
+[build]
+  builder = "paketobuildpacks/builder:base"
+
+[env]
+  PORT = "8080"
+
+[experimental]
+  allowed_public_ports = []
+  auto_rollback = true
 
 [[services]]
+  http_checks = []
   internal_port = 8080
+  processes = ["app"]
   protocol = "tcp"
+  script_checks = []
 
   [services.concurrency]
     hard_limit = 25
     soft_limit = 20
+    type = "connections"
 
   [[services.ports]]
     handlers = ["http"]
-    port = "80"
+    port = 80
 
   [[services.ports]]
     handlers = ["tls", "http"]
-    port = "443"
+    port = 443
 
   [[services.tcp_checks]]
-    interval = 10000
-    timeout = 2000
+    grace_period = "1s"
+    interval = "15s"
+    restart_limit = 0
+    timeout = "2s"
 ```
 
 The `flyctl` command will always refer to this file in the current directory if it exists, specifically for the `app` name/value at the start. That name will be used to identify the application to the Fly service. The rest of the file contains settings to be applied to the application when it deploys.