From 640463ca4ddad9d439e5905e12864bfb6c41d9ab Mon Sep 17 00:00:00 2001 From: Matthias Haeussler Date: Mon, 29 Jul 2024 09:49:07 +0200 Subject: [PATCH] more linebreaks --- README.md | 14 ++++++++------ 1 file changed, 8 insertions(+), 6 deletions(-) diff --git a/README.md b/README.md index 8a6bb74..0b4f824 100644 --- a/README.md +++ b/README.md @@ -16,21 +16,23 @@ This will be the default for running this lab. All exercises are described accor To run the lab on your local machine, you'll need to have [Docker](https://docs.docker.com/engine/install/), [VS Code](https://code.visualstudio.com/download), and the [Dev Containers extension](https://marketplace.visualstudio.com/items?itemName=ms-vscode-remote.remote-containers) installed. When you open this repository with a locally installed VS Code instance, you'll see a prompt in the bottom right corner. -
+

![Prompt to open the repo inside a Dev container](tutorial/content/exercises/introduction/images/prompt.png) Press `Reopen in Container` to allow VS Code to use the [devcontainer.json](.devcontainer/devcontainer.json) specification to set up the IDE. If you missed the prompt hit Ctrl + Shift + P (on Mac Command + Shift + P) and type `Dev Containers: Rebuild and Reopen in Container`. After that the [devcontainer spec](.devcontainer.json) will pull all needed dependencies to build and run the devcontainer in which we will work on the lab content. This can take a bit, so be patient. -
+

![Open the terminal](tutorial/content/exercises/introduction/images/open-terminal.png) When you run an application that exposes a port, VS Code will notify you that it is accessible. To open the application, just click `Open in Browser` or open your Browser manually and type the URL yourself. +

![Open the browser](tutorial/content/exercises/introduction/images/open-port.png) When you missed the prompt you can see the open ports in the `PORTS` tab. +

![Where to find the forwarded ports](tutorial/content/exercises/introduction/images/ports.png) ### Running the lab remotely @@ -41,7 +43,7 @@ To utilize either option, you'll need a personal GitHub account. In both cases, a VSCode Instance in your browser will be opened automatically and you are immediately ready to go. Normally Codespaces and Gitpod should work in an almost identical way as a local devcontainer setup. However these platforms are subject to change and we can't keep the lab tested continously on all remote platforms. - +

[![Open in GitHub Codespaces](https://github.com/codespaces/badge.svg)](https://codespaces.new/NovatecConsulting/opentelemetry-training) [![Open in Gitpod](https://gitpod.io/button/open-in-gitpod.svg)](https://gitpod.io/#https://github.com/NovatecConsulting/opentelemetry-training) ### Differences between local and remote way of running the lab @@ -49,15 +51,15 @@ Normally Codespaces and Gitpod should work in an almost identical way as a local Even though the experience with using a local or browser-based VS Code is fairly similar, one thing you need to take care of is the variation in hostnames and ports. In a local environment, you can use the combination of `localhost` and the corresponding port. In a remote environment, this will not work when trying to access endpoints via a browser. This is the ports tab of a local VS Code environment: - +

![VS Code ports](tutorial/content/exercises/introduction/images/vscode_ports.png) This is the ports tab of a GitHub Codespaces environment: - +

![Codespaces ports](tutorial/content/exercises/introduction/images/codespaces_ports.png) This is the ports tab of a GitHub Codespaces environment: - +

![Gitpod ports](tutorial/content/exercises/introduction/images/gitpod_ports.png) You can see that they look almost identical. In some cases, you might have to hover over the address to reveal a link.