pull down to refresh
0 sats \ 11 replies \ @GlobalThreat 12 Dec 2023
why not just provide a docker-compose file?
reply
2 sats \ 0 replies \ @Rsync25 OP 12 Dec 2023
Good idea.
reply
0 sats \ 9 replies \ @r3drun3 12 Dec 2023
Hi, I am the one that wrote the tutorial!
I did not provide a docker compose file because there is nothing to compose, it is a single container :)
reply
0 sats \ 0 replies \ @Rsync25 OP 12 Dec 2023
Congrats by the tutorial! It is awesome!
Good!
reply
0 sats \ 7 replies \ @GlobalThreat 12 Dec 2023
still easier than remember some command line. I havfe many compose files for single containers
reply
0 sats \ 6 replies \ @r3drun3 12 Dec 2023
The purpose of the tutorial is to get one hands dirty.
If you only run docker-compose up what is the point of a practical tutorial?
Also in that specific case you dont need docker compose because you are dealing with a single container.
reply
0 sats \ 4 replies \ @GlobalThreat 12 Dec 2023
i also like to have an .env file that docker-compose.yml can read from to define ports, upload directories and anything else that is configurable. Not sure why you're opposed to docker-compsoe.
reply
0 sats \ 3 replies \ @r3drun3 12 Dec 2023
I am not opposed to it!
I am just saying that I dont see the point for a simple hands on tutorial.
reply
0 sats \ 2 replies \ @GlobalThreat 12 Dec 2023
i gotcha. yeah i guess that makes sense. i just saw all the work i had to do and said "nevermind" because there was no docker-compose.
reply
0 sats \ 1 reply \ @r3drun3 12 Dec 2023
My purpose was to bang people heads against an atomic node deployment.
Docker compose is way overkill for my purpose...why dont use kubernetes then :P
view replies
0 sats \ 0 replies \ @GlobalThreat 12 Dec 2023
i like to run multiple nodes
reply