Here's a workspace with our same Sinatra app from before.

Notice I made sure to add set bind 0, 0, 0, 0 right after

the require Sinatra lines so that I can connect to the app from a remote computer.

We already have a route to accept get requests for the /apple path and

returns to main HTML in the response.

We can support additional paths by adding additional routes, one after another.

So let's go down here to the bottom,

we'll add another get route for a path of /banana.

We'll give it a block which will be used to determine Sinatra's response.

Now let's go up here and make this a level one heading, while I'm thinking about it.

And we'll do the same here, level one heading.

Here's a ripe banana, close our heading, and close our string.

And then we'll set up a third route.

Also for get request, and we'll give this one a path of /carrot.

Set up a block.

Level one heading.

Here's a crunchy carrot.

We'll be sure to save that, and then we need to go to the console and run it.

Ruby produce.rb.

Now we can go into the preview and reload, and there's our /apple path.

And now we can change the path from /apple to /banana.

And a get request for that path will be sent instead.

When a request comes into a Sinatra app,

it looks through the routes you've defined one by one from top to bottom.

The first routes match both the request method, get in this case,

and the resource path will be chosen, and the accompanying Ruby block will be run.

So this request will match the GET /banana route in our app, the block for

that route will be run, and we'll get different HTML in response.

We can also change the path to /carrot,

Which will match the third route and run the third block.

For additional practice you should try adding more get routes to our

produce.rb app now.

You can also try returning different HTML strings from the existing routes.

We'll see you in the next stage where we'll be talking about a Sinatra feature

that will let you render not just short strings but an entire HTML page.