removed task titles from the descriptions in the last two lessons

Author: sofiiako

Building the Gateway Application/Add a Dockerfile and requirements.txt/task.md

@@ -1,5 +1,3 @@
-## Add Dockerfile and requirements.txt
-
 ### Task 
 Add the files necessary to run the gateway app as a Docker container.
 

Building the Gateway Application/Define routes/task.md

@@ -1,5 +1,3 @@
-## Define Routes
-
 We added the four functions needed in our gateway application for routing requests (in addition to `index()`, which doesn't really do anything).
 Each of these four functions will send a request to the other application.
 In this task, you will add the appropriate routes to all of them.

Building the Gateway Application/Delete Device/task.md

@@ -1,5 +1,3 @@
-## Delete Resource
-
 In this task, we will define the `delete_device` function, which will:
 - Forward the delete request to the relevant endpoint in `invsys`.
 - Forward the response back to the client by creating a `Response` object from the received `response`.

Building the Gateway Application/Get Devices/task.md

@@ -1,5 +1,3 @@
-## Get Devices
-
 In this task, we will define the `get_devices` function, which will:
 - Forward the request to the relevant endpoint in `invsys` (depending on the URL: if the item ID is provided,
 it needs to be added to the route, which in `invsys` will result in calling the `get` endpoint in the function `device`)

Building the Gateway Application/Introduction/task.md

@@ -1,5 +1,3 @@
-# Gateway Application
-
 The next step will be creating an API gateway backend, which acts as a router for client requests.
 This means our final application will consist of two backend components: the inventory
 manager and the API gateway.

Building the Gateway Application/Post Device/task.md

@@ -1,5 +1,3 @@
-## POST Resource
-
 In this task, we will define the `post_device` function, which will:
 - Get the payload from our incoming request.
 - Forward the POST request to the relevant endpoint in invsys. Do not forget the payload!

Building the Gateway Application/Put Device/task.md

@@ -1,5 +1,3 @@
-## Put Resource
-
 In this task we will define the `put_device` function, which will:
 - Get the payload from our incoming request.
 - Forward the PUT request to the relevant endpoint in `invsys`. Do not forget the payload!

Composing the System/Deploying without Docker/task.md

@@ -1,6 +1,3 @@
-## Deploying locally without Docker
-
-
 While this course is focused on deploying with Docker, you can also deploy locally without it. 
 
 You will need to change the routes in the `gateway`:

Composing the System/Docker-compose/task.md

@@ -1,4 +1,3 @@
-## Composing our system
 Now we have two Flask apps: Invsys and Gateway. 
 We want them both to be deployed, and we want Gateway to be able to send 
 requests to Invsys using `invsys` instead of a specific IP.

Composing the System/What's next/task.md

@@ -1,5 +1,3 @@
-## What else to explore
-
 Here are some recommended resources for further reading:
 
 [Flask by example: Part 1](https://realpython.com/flask-by-example-part-1-project-setup/) — a tutorial.