You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* When you're prompted to verify the detected framework for the project, **Python - Flask** or **Python - Django**, reply `y`.
35
-
* You are then prompted to **Connect to an IBM Cloud app**. Select either the **Generate assets, create a new IBM Cloud app and connect to it** or **Generate assets without connecting to an IBM Cloud app** options to your app.
35
+
* You are then prompted to **Connect to an IBM Cloud app**. Select either the **Generate assets, create a new IBM Cloud app and connect to it** or **Generate assets without connecting to an IBM Cloud app** options to connect your app.
36
36
* The `enable` command can also create services and bind them to your app. For this basic example, reply `n`.
37
37
38
38
See the following sample output:
@@ -125,7 +125,7 @@ ibmcloud dev deploy
125
125
## What to do if your enabled app does not build or deploy
126
126
{: #build-failure-python}
127
127
128
-
Not all apps are successfully enabled by the `enable` command. For example, the following error might occur when the project name is different from the directory name that contains the `wsgi.py` and `settings.py` files:
128
+
Not all apps are successfully enabled by the `enable` command. For example, the following error might occur when the project name differs from the directory name that contains the `wsgi.py` and `settings.py` files:
## Am I required to use the latest version of the {{site.data.keyword.cloud_notm}} CLI?
16
+
## Is it required to use the latest version of the {{site.data.keyword.cloud_notm}} CLI?
17
17
{: #cli-latest-version}
18
18
19
19
Yes, you must use the latest version. You can check which version you are using by running the following command:
@@ -23,7 +23,7 @@ ibmcloud -v
23
23
```
24
24
{: codeblock}
25
25
26
-
## How do I update my CLI?
26
+
## How to update the CLI
27
27
{: #cli-update-version}
28
28
29
29
Run the following command to update to the latest version of the CLI:
@@ -33,26 +33,26 @@ ibmcloud update
33
33
```
34
34
{: codeblock}
35
35
36
-
## Can I get notified about new releases of the CLI?
36
+
## How to be notified about new CLI releases?
37
37
{: #cli-get-notified}
38
38
39
-
Yes, you stay up to date on new releases of the CLI as they become available. Subscribe to the [{{site.data.keyword.cloud_notm}} CLI releases repository](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/){: new_window} ![External link icon](../../../icons/launch-glyph.svg"External link icon")
39
+
Yes, you stay up-to-date on new releases of the CLI as they become available. Subscribe to the [{{site.data.keyword.cloud_notm}} CLI releases repository](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/){: new_window} ![External link icon](../../../icons/launch-glyph.svg"External link icon")
40
40
41
41
## What is the file structure for {{site.data.keyword.cloud_notm}} applications?
42
42
{: #cli-file-structure}
43
43
44
44
Applications that are created or enabled from the CLI come with pre-configured settings encapsulated in the `cli-config.yml` file. The `cli-config.yml` contains default entries that are used by the commands of the CLI that can be overridden by values that are passed through the command line.
45
45
46
-
Apps that have deployed to a DevOps toolchain may also contain files such as `toolchain.yml` and `pipeline.yml`. Apps that are being manually deployed can contain a `manifest.yml` and Helm chart files (for deployment to Cloud Foundry or Kubernetes, for example).
46
+
Apps that are deployed to a DevOps toolchain can also contain files such as `toolchain.yml` and `pipeline.yml`. Apps that are being manually deployed can contain a `manifest.yml` and Helm chart files (for deployment to Cloud Foundry or Kubernetes, for example).
47
47
48
48
## How are local containers used?
49
49
{: #cli-faq-containers}
50
50
51
51
The {{site.data.keyword.dev_cli_long}} CLI plug-in uses two containers to facilitate building and testing your app. The first is the tools container, which contains the necessary utilities to build and test your app. The `Dockerfile` for this container is defined by the [`dockerfile-tools`](/docs/cli/idt?topic=cloud-cli-idt-cli#command-parameters) parameter. You might think of it as a development container, as it contains the tools that are normally used for development of a particular runtime.
52
52
53
-
The second container is the run container, which closely mimics the actual runtime environment of your app once that it is deployed to the cloud. This container is in a form that is suitable to be deployed for use, for example, in {{site.data.keyword.cloud_notm}}. As a result, an entry point is defined that starts your app. When you select to run your app through the {{site.data.keyword.dev_cli_long}} CLI Plug-in CLI, it uses this container. The `Dockerfile` for this container is defined by the [`dockerfile-run`](/docs/cli/idt?topic=cloud-cli-idt-cli#run) parameter.
53
+
The second container is the run container, which closely mimics the actual runtime environment of your app once it is deployed to the cloud. This container is in a form that is suitable to be deployed for use, for example, in {{site.data.keyword.cloud_notm}}. As a result, an entry point is defined that starts your app. When you select to run your app through the {{site.data.keyword.dev_cli_long}} CLI plug-in CLI, it uses this container. The `Dockerfile` for this container is defined by the [`dockerfile-run`](/docs/cli/idt?topic=cloud-cli-idt-cli#run) parameter.
54
54
55
-
## How do I deploy existing code?
55
+
## How to deploy existing code?
56
56
57
57
To deploy an existing code base, see [Generating deployment and cloud enablement assets](/docs/apps?topic=creating-apps-create-deploy-app-cli#byoc-cli).
0 commit comments