This is currently WIP.

Managed to get everything working so far, the last thing missing is to properly print instructions. Pulling instructions from a list like all other data wouldn't be the problem, but I would also like to print generic output for instructions that run and are not cached.

Example:

RUN ls -la

should output something like

total 208
drwxr-xr-x  21 kg  staff    672 Dec 12 09:36 .
drwxr-xr-x@  9 kg  staff    288 Dec  5 00:17 ..
-rw-r--r--   1 kg  staff    219 May 21  2019 .editorconfig
drwxr-xr-x  15 kg  staff    480 Dec 12 11:01 .git
-rw-r--r--   1 kg  staff     28 Jun  1  2018 .gitignore
-rw-r--r--   1 kg  staff   2812 May 21  2019 .travis.yml

but I'm not sure how to implement this. Any ideas?

Also, hope the current code is not that horrifying. 😬

I just tried to implement a Docker plugin based on #64. It basically works but I couldn't make the SHA256 generation work as there are type conflicts.

The following error is thrown in src/docker.rs:22:

return sha256.result();
           ^^^^^^^^^^^^^^^ expected struct `std::string::String`, found struct `generic_array::GenericArray`

Corresponding code:

fn gen_hash() -> String {
    let mut rng = rand::thread_rng();
    let mut sha256 = Sha256::new();
    sha256.input(
        rng.sample_iter(&Alphanumeric)
        .take(30)
        .collect::<String>()
    );
    return sha256.result();
}

I tried several things and searched for ways to convert from one type to a string but I had no luck. I also found no information about returning the hash result as a string directly. Perhaps this is an easy fix but I am not familiar with Rust so I am stuck at the moment.

Could you create a docker image and push to docker hub for running it without downloading any additional files? This seems to be quick option to get new users as they only have to run single command instead of trying to download correct binaries and then figure out how to launch them.

I've translated botnet module into Rust. As the translation is almost word-to-word, please feel free to tell me if I can rewrite something in more rust-ish way.

Reticulating Splines is a classic "loading screen phrase" that first appeared in Sim City 2000.

This modules combines the spinner from FGRibreau/spinners with these phrases.

At random intervals, the text appears in red, yellow or blue.

This is an initial implementation of the module julia. It simulates the process of updating all the packages in a project.

There are still some features missing:

• [x] ~downloading artifacts~
• [x] ~building artifacts~
• [x] ~possible old manifest format~
• [x] ~garbage collection~
• [ ] dynamic package precompilation

If there is some interest, I can work on adding them.

Updated asciinema recording (others are available on my account):

Made a yaml file to pack genact as a snap, using snapcraft. Did a rough test, and put genact in a fully confined enviroment; Would be nice to make more users looks much busier and still feeling safe :)

FYI, genact is going to be included in the FreeBSD ports collection soon.

The PR is available here: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=228306

When it's pulled it will be able to install a prebuilt genact package with:

pkg install genact

Nice and easy. You can start generating nonsense in no time.

Cheers! 😄

What does this PR do?

It adds burst mode to the bootlog module

Description of Task to be completed?

• The bootlog module should behave a bit more realistically in that it should sometimes burst a bunch of lines really quickly

How should this be manually tested?

• Run cargo run -- -m bootlog in the project
• The output should be printed in quick succession from time to time.

Maybe I can cut the size down by compressing stuff in data/ during build time (with build.rs) and then decompressing it during runtime. Gotta investigate.

I added some lines to the Dockerfile to utilize multi-stage builds. This reduces the image size to around ~60MB by only adding the final genact binary to the image.

Thanks for creating such a handy little tool. It would be great if a percentage could be shown on the screen that correlated with the time given in the -e or -exitafter switches, so that the percentage complete was calculated based on the remaining time until the process will stop.

Maybe it can use a fixed row at the bottom of the terminal, with the output continuing above it?