openshift-docs/modules/getting-started-web-console-deploying-python-app.adoc

// Module included in the following assemblies:
//
// * getting-started/openshift-web-console.adoc

:_content-type: PROCEDURE
[id="getting-started-web-console-deploying-python-app_{context}"]
= Deploying a Python application

The following procedure deploys a back-end service for the `parksmap` application. The Python application performs 2D geo-spatial queries against a MongoDB database to locate and return map coordinates of all national parks in the world.

The deployed back-end service that is `nationalparks`.

.Prerequisites

* You are logged in to the {product-title} web console.
* You are in the *Developer* perspective.
* You have a deployed image.

.Procedure

. From the *+Add* view in the *Developer* perspective, click *Import from Git* to open a dialog.
. Enter the following URL in the Git Repo URL field:
[x-]`https://github.com/openshift-roadshow/nationalparks-py.git`
+
A builder image is automatically detected.
+
[NOTE]
====
If the detected builder image is Dockerfile, select *Edit Import Strategy*. Select *Builder Image* and then click *Python*.
====
. Scroll to the *General* section.
. Ensure that you have the current values for the following:
.. Application: `national-parks-app`
.. Name: `nationalparks`
. Select *Deployment* as the *Resource*.
. Select *Create route to the application*.
. In the *Advanced Options* section, click *Labels* and add labels to better identify this deployment later. Labels help identify and filter components in the web console and in the command line. Add the following labels:
.. `app=national-parks-app`
.. `component=nationalparks`
.. `role=backend`
.. `type=parksmap-backend`
. Click *Create*.
. From the *Topology* view, select the `nationalparks` application.
+
[NOTE]
====
Click the *Resources* tab. In the *Builds* section, you can see your build running.
====