From b27b7bfd4e95b35a5dbce225ac135287a8bbdb24 Mon Sep 17 00:00:00 2001 From: Raúl Benencia Date: Tue, 8 Jan 2019 19:48:29 -0800 Subject: Move screenshots to docs/screenshots --- README.md | 6 +++--- docs/screenshots/shoelaces-frontend-1.png | Bin 0 -> 49354 bytes docs/screenshots/shoelaces-frontend-2.png | Bin 0 -> 38786 bytes docs/screenshots/shoelaces-overview.png | Bin 0 -> 21554 bytes shoelaces-frontend-1.png | Bin 49354 -> 0 bytes shoelaces-frontend-2.png | Bin 38786 -> 0 bytes shoelaces-overview.png | Bin 21554 -> 0 bytes 7 files changed, 3 insertions(+), 3 deletions(-) create mode 100644 docs/screenshots/shoelaces-frontend-1.png create mode 100644 docs/screenshots/shoelaces-frontend-2.png create mode 100644 docs/screenshots/shoelaces-overview.png delete mode 100644 shoelaces-frontend-1.png delete mode 100644 shoelaces-frontend-2.png delete mode 100644 shoelaces-overview.png diff --git a/README.md b/README.md index 1bfe2d8..a76ef52 100644 --- a/README.md +++ b/README.md @@ -22,7 +22,7 @@ As soon as Shoelaces starts, the service will be patiently waiting for servers to boot. If no servers are detected, you'll simply see a spinner in the web UI, as can be seen in the screenshot. -![Shoelaces frontend - Waiting for hosts](shoelaces-frontend-1.png) +![Shoelaces frontend - Waiting for hosts](docs/screenshots/shoelaces-frontend-1.png) The URL `localhost:8081` will actually point to wherever you are running your Shoelaces instance. It must be reachable by the booting hosts. @@ -30,7 +30,7 @@ Shoelaces instance. It must be reachable by the booting hosts. The following picture shows a high level overview of how a server notifies Shoelaces that it's ready for booting. -![Shoelaces overview](shoelaces-overview.png) +![Shoelaces overview](docs/screenshots/shoelaces-overview.png) In this graph we can see that as soon as the server boots using network boot, we instruct the machine to switch to an [iPXE](https://ipxe.org/) ROM. We do this @@ -50,7 +50,7 @@ guessed, will be pointing to Shoelaces. If there was no automated installation configured for the booting server, you'll be able to select an option to bootstrap it in the Shoelaces UI. -![Shoelaces frontend - Host detected](shoelaces-frontend-2.png) +![Shoelaces frontend - Host detected](docs/screenshots/shoelaces-frontend-2.png) A couple of things can be said about this screenshot: diff --git a/docs/screenshots/shoelaces-frontend-1.png b/docs/screenshots/shoelaces-frontend-1.png new file mode 100644 index 0000000..96518e9 Binary files /dev/null and b/docs/screenshots/shoelaces-frontend-1.png differ diff --git a/docs/screenshots/shoelaces-frontend-2.png b/docs/screenshots/shoelaces-frontend-2.png new file mode 100644 index 0000000..4864303 Binary files /dev/null and b/docs/screenshots/shoelaces-frontend-2.png differ diff --git a/docs/screenshots/shoelaces-overview.png b/docs/screenshots/shoelaces-overview.png new file mode 100644 index 0000000..812fa8b Binary files /dev/null and b/docs/screenshots/shoelaces-overview.png differ diff --git a/shoelaces-frontend-1.png b/shoelaces-frontend-1.png deleted file mode 100644 index 96518e9..0000000 Binary files a/shoelaces-frontend-1.png and /dev/null differ diff --git a/shoelaces-frontend-2.png b/shoelaces-frontend-2.png deleted file mode 100644 index 4864303..0000000 Binary files a/shoelaces-frontend-2.png and /dev/null differ diff --git a/shoelaces-overview.png b/shoelaces-overview.png deleted file mode 100644 index 812fa8b..0000000 Binary files a/shoelaces-overview.png and /dev/null differ -- cgit v1.2.3