From f7ae86711acdf3bd89e5ad87ca0c1e4930f942c7 Mon Sep 17 00:00:00 2001 From: Chad Jessup Date: Wed, 18 Mar 2020 22:48:10 -0700 Subject: [PATCH] Making 'tye run' explicit at end of instructions (#140) --- docs/frontend_backend_run.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/frontend_backend_run.md b/docs/frontend_backend_run.md index 76aa3a44..34acac10 100644 --- a/docs/frontend_backend_run.md +++ b/docs/frontend_backend_run.md @@ -204,7 +204,7 @@ Now that we have two applications running, let's make them communicate. By defau ``` -7. Run the project and the `frontend` service should be able to successfully call the `backend` service! +7. Run the project with [`tye run`](commandline/tye-run.md) and the `frontend` service should be able to successfully call the `backend` service! When you visit the `frontend` service you should see a table of weather data. This data was produced randomly in the `backend` service. The fact that you're seeing it in a web UI in the `frontend` means that the services are able to communicate.