From 418fe2b5a01d8f62c0f4d94399f6a58ca300f223 Mon Sep 17 00:00:00 2001 From: philbob Date: Sat, 28 Dec 2024 00:15:56 +0000 Subject: [PATCH] more sensible README explaining how this shit works something more than just "it just works" --- README.md | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index cf22004..b84ea4d 100644 --- a/README.md +++ b/README.md @@ -27,4 +27,21 @@ dependencies (for debian): what I've installed: 1.4 everything is ready? then we start up container sudo docker-compose up - and connect with localhost (by default it should be localhost:3000) \ No newline at end of file + and connect with localhost (by default it should be localhost:3000) + +2. because we start with monitoring what's going on our own server, we will deploy prometheus and node_exporter now. + let's start with node_exporter becasue this is the source of data about our server + + 2.1 add docker config for node exporter + + 2.2 add docker config for prometheus + +HUGE DISCLAIMER ABOUT NETWORKING: +technically, every application has own container which mean it also has its own networking rules. for tests, I connected it together that: + +1. turn on containers: docker-compose up -d +2. list working containers: docker ps +3. inspect them: docker inspect +4. look for "NetworkSettings" and sub-category Networks +5. look for value in "IPAddress" because this is our "localhost" for particular container +6. take this value and get access to container with this pattern http://:assigned_port \ No newline at end of file