Docker - Revision history

B3b0tUzR: /* Bot config */

2024-12-05T21:03:32Z

Bot config

B3b0tUzR at 20:59, 11 April 2024

2024-04-11T20:59:41Z

B3b0tUzR at 16:41, 26 January 2024

2024-01-26T16:41:44Z

B3b0tUzR at 15:22, 26 January 2024

2024-01-26T15:22:12Z

B3b0tUzR at 15:03, 26 January 2024

2024-01-26T15:03:08Z

B3b0tUzR at 15:01, 26 January 2024

2024-01-26T15:01:12Z

B3b0tUzR at 15:00, 26 January 2024

2024-01-26T15:00:38Z

B3b0tUzR at 14:56, 26 January 2024

2024-01-26T14:56:59Z

B3b0tUzR at 14:56, 26 January 2024

2024-01-26T14:56:45Z

B3b0tUzR at 19:50, 22 January 2024

2024-01-22T19:50:18Z

@@ Line 150: / Line 150: @@
 </pre>
-On Windows this can't properly, so we will let Docker manage volumes for us that will soon be explorable at network location \\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\
+On Windows this can't work properly, so we will let Docker manage volumes for us that will soon be explorable at network location \\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\
 https://stackoverflow.com/questions/61083772/where-are-docker-volumes-located-when-running-wsl-using-docker-desktop
@@ Line 160: / Line 160: @@
 Windows only : possibly set permissive rights on those folders/files (select all, right-click > Properties > Security) so our container access them.
 ===== Run =====

@@ Line 224: / Line 224: @@
 - find & delete the bot container (docker ps -a ; docker rm fullid)
-- find & delete the bot image (docker image ls ; docker rm imagename)
+- find & delete the bot image (docker image ls ; docker image rm imagename)
 - rebuild the bot image (docker compose build servicename --no-cache)

← Older revision		Revision as of 16:41, 26 January 2024
Line 150:		Line 150:
	</pre>		</pre>

−	On Windows this can't properly, so we will let Docker manage volumes for us that will soon be ~~accessible~~ at \\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\	+	On Windows this can't properly, so we will let Docker manage volumes for us that will soon be explorable at network location \\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\
		+
		+	https://stackoverflow.com/questions/61083772/where-are-docker-volumes-located-when-running-wsl-using-docker-desktop

@@ Line 144: / Line 144: @@
 For that reason we will extract some files within the image we built earlier, and save them at host level to protect them.
-To do this, we will now run this long line on Linux from our chosen folder :
+To do this, we will now run this long line on Linux from within upper chosen folder to get bindable datas :
 <pre>
@@ Line 150: / Line 150: @@
 </pre>
-On Windows a part of this shouldn't work at all, so we will only obtain compressed datas into our chosen folder :
+On Windows this can't properly, so we will let Docker manage volumes for us that will soon be accessible at \\wsl$\docker-desktop-data\version-pack-data\community\docker\volumes\
-In any case we get 5 new folders ("Conf" "Custom" "Extras" "log" "Text") in chosen folder - where our 3 Docker config files are also.
+In any case we'll get 5 new folders ("Conf" "Custom" "Extras" "log" "Text") in chosen folder - where our 3 Docker config files are also.
 Note : in upper case SQL3 we'll also soon have a "db" folder later at the same place, once we'll have our DB container started for first time.
@@ Line 174: / Line 168: @@
 </pre>
-Your bot should now load (after launching its DB if some) and, as it's our first run, ask to fill up credentials informations.
+Your bot should now load (after launching its DB if some), check its updates then show its ip within Docker network.
 So give him account name, pass, character, server and also owner and superadmin(s) plus few more questions.
@@ Line 180: / Line 176: @@
 Then you're asked for the SQL part. In upper cases SQL1/2 you should already have everything needed here.
-For upper case SQL3 you are just missing one information (SQL server ip) obtainable by 2 ways :
+For upper case SQL3 you db ip should but the same than bot but end in .2 (as .1 should be host and .3 the bot itself).
-Continue the setting up where you stopped earlier, then bot will start and create all his DB entries, and endly come online !
+Finish the setting up, then bot will create all his DB entries, and endly come online !
 NB : expect some deep caching at very first run keeping the bot busy for a minute or two. If anything goes wrong, restart containers (see below).
@@ Line 216: / Line 194: @@
 To see realtime stats of container(s) : docker stats (Ctrl+c to exit)
-To get realtime log of a container : docker logs -f container_name_or_id (Ctrl+c to exit which will NOT shutdown bot/container)
+To passively check realtime log of a container : docker logs -f container_name_or_id (Ctrl+c to exit which will NOT shutdown bot/container)
-To enter a container interactively : docker exec -it container_name_or_id sh (Ctrl+p Ctrl+q to exit without shutting down neither)
+To execute container interactively : docker exec -it container_name_or_id sh (Ctrl+p Ctrl+q for the same result that upper)
 To copy from a running container : docker cp container_name_or_id:/path/to/stuff.ext .
-The same towards a running container : docker cp stuff.ext container_name_or_id:/path/to/
+The same towards a running container : docker cp stuff.ext container_name_or_id:/path/to/copy/to
@@ Line 234: / Line 214: @@
-If Bebot git code was patched, such container restart upper should render it correctly auto-updated.
+If Bebot git code was patched, such container restart upper should quickfix to auto-update it.
-For best certainty you also could delete bot image (its container once stopped/removed) and rebuild it with --no-cache parameter added :
+For best reliability you also can delete bot image (its container once stopped/removed) and rebuild it with --no-cache parameter added :
 - stop all (docker compose down ; docker stop containername)
@@ Line 268: / Line 246: @@
 - your various elements ip, port, state and availability
-- you credentials (check bot's Conf folder, Docker's compose for SQL3)
+- you credentials (check bot's Conf folder in all cases, Docker's compose for case SQL3)
 If needed to make house cleaning (assuming you've made <span style="color:#BB0000">BACKUPS</span> of sensible datas you could lose below !) :
-To renew the container content : docker compose down (possibly --volumes param added)
+To stop the containers : docker compose down (possibly --volumes param added)
 To delete the recent containers : docker rm $(docker ps -a -q)

← Older revision		Revision as of 15:03, 26 January 2024
Line 118:		Line 118:
	3: "botonly" (in upper cases SQL1/2) or "botplusdb" (in upper case SQL3).		3: "botonly" (in upper cases SQL1/2) or "botplusdb" (in upper case SQL3).

		+
		+	Once inside the folder meeting your requirements, you can check (ls or dir) its content :
		+
		+	You get those 3 files : docker-compose.yml \| docker-entrypoint.sh \| Dockerfile

	Note : you could edit Dockerfile and change PHP version for whatever you like ; more details on its modules/config at https://www.php.net/docs.php		Note : you could edit Dockerfile and change PHP version for whatever you like ; more details on its modules/config at https://www.php.net/docs.php

← Older revision		Revision as of 15:01, 26 January 2024
Line 107:		Line 107:
	Once the software is installed, you first have to build runnable images from Bebot Docker preset configs :		Once the software is installed, you first have to build runnable images from Bebot Docker preset configs :

−	Get them from https://github.com/bitnykk/DockerBeBot/ (download the .zip or use git clone)	+	Get them from https://github.com/bitnykk/DockerBeBot/ (download/decompress the .zip or use git clone)

@@ Line 110: / Line 110: @@
-Then in command line, enter wanted folder : "official" to run latest stable bot, or "sandbox" for some dev/beta testing.
+Then in command line, enter (cd) into the folder corresponding to your situation. Their name have 3 parts :
-In chosen sublevel, opt for the corresponding version : "botonly" (in upper cases SQL1/2) or "botplusdb" (in upper case SQL3).
+: "linux" or "windows", which depends on your host Operating System,
-You could edit Dockerfile and change PHP version for whatever you'd like ; more details on its modules and config at https://www.php.net/docs.php
+: "official" to run latest stable bot, or "sandbox" for some dev/beta testing,
 In upper case SQL3, you'd also have to setup your SQL credentials within docker-compose.yml (4 values to modify under "environment" part).

@@ Line 39: / Line 39: @@
 Also notice that we'll often refer to "console" below. This is a text command line prompt we'll often need.
 For Linux/Mac it should be available into your shortcuts.
 For Windows you'd have to open menu and type "cmd" or "powershell".
 Just make sure you're installed and ready to type, then continue to next section.

@@ Line 38: / Line 38: @@
-Just make sure you're properly installed then continue to next section.
+Also notice that we'll often refer to "console" below. This is a text command line prompt we'll often need.
@@ Line 49: / Line 53: @@
 SQL2: you opted for a local service on host ; so you'd usually go for usual SQL port (3306) but instead of 127.0.0.1 default ip we'd advice you default docker0 network ip 172.17.0.1
-SQL3: you're about to run a container for that ; you can skip this part fully as we'll explain you how to set this up correctly later in "build" section, it's the simplest in fact !
+SQL3: you are about to run a container for that ; you can skip this part fully as we'll explain you how to set this up correctly later in "build" section, it's the simplest in fact !

← Older revision		Revision as of 19:50, 22 January 2024
Line 187:		Line 187:
	Continue the setting up where you stopped earlier, then bot will start and create all his DB entries, and endly come online !		Continue the setting up where you stopped earlier, then bot will start and create all his DB entries, and endly come online !

−	NB : expect some deep caching at very first run keeping the bot busy for a minute or two.	+	NB : expect some deep caching at very first run keeping the bot busy for a minute or two. If anything goes wrong, restart containers (see below).