<commit_before># docker-gentoo-steemd
`steemd` built inside a Docker container using a Gentoo base with size optimization

In the `dkr` directory is a short shell script that sets some handy aliases, which you
will need to run this docker container:

    cd dkr
    source init.sh

Then you can type `halp` and it will show you the short commands to perform all the 
functions:

        dkr  "sudo docker"
       .run  "sudo docker run -v ~/docker-gentoo-portage/data:/work -d  true --name docker-gentoo-portage -t docker-gentoo-portage"
     .enter  "sudo docker exec -it docker-gentoo-portage bash"
       .log  "sudo docker logs --tail  30 -f docker-gentoo-portage"
      .stop  "sudo docker stop docker-gentoo-portage"
        .rm  "sudo docker rm docker-gentoo-portage"
     .build  "sudo docker build -t docker-gentoo-portage ."

I usually string these commands together when I am developing the Dockerfile, so
to build it, if it was already built and you have changed the Dockerfile, you will need
to run it like this:

    .stop;.rm;.build

which will stop the existing one with the name (by default in the init file, it is
`docker-gentoo-steemd`), remove the FS layers and start a build.

By default it starts up a No-Op command so you can manually enter to start up `steemd`,
but you can change this to automatically start steemd in the last line of the Dockerfile.
To run and enter the container:

    .run;.enter

The data directory contains a volume that is mounted inside the container as `/work`<commit_msg>edited README.md to describe improvements in the init.sh<commit_after># docker-gentoo-steemd
`steemd` built inside a Docker container using a Gentoo base with size optimization

In the `dkr` directory is a short shell script that sets some handy aliases, which you
will need to run this docker container:

    cd dkr
    source init.sh

Then you can type `halp` and it will show you the short commands to perform all the 
functions. The script stores its own location automatically so all commands will work 
no matter where you move in your filesystem. The script can be edited with the command:
`.editsh`. Note that the halp command simply processes the script itself to produce
the output, the code is the documentation, is the code.

I usually string these commands together when I am developing the Dockerfile, so
to build it, if it was already built and you have changed the Dockerfile, you will need
to run it like this:

    .stop;.rm;.build

which will stop the existing one with the name (by default in the init file, it is
`docker-gentoo-steemd`), remove the FS layers and start a build.

By default it starts up a No-Op command (tail -f /dev/null) so you can manually enter to 
start up `steemd`,but you can change this to automatically start steemd in the last line of the Dockerfile.
To run and enter the container:

    .run;.enter

You can also directly spawn `steemd` with the command `.steemd`

The data directory contains a volume that is mounted inside the container as `/work`
{'fraction_non_alphanumeric': 0.0546538588936734, 'fraction_numerical': 0.000662471016893011, 'mean_word_length': 3.617737003058104, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '5115015', 'n_tokens_mistral': 874, 'n_tokens_neox': 824, 'n_words': 467}