lancelet / bored-robot Goto Github PK

The app should do what the docker-fu script currently does (for the shell functions in it).

• framework: subcommand and option parsing
• prototype using standard haskell and mocks
• actual implementation using the effects implemented
  Depends on the effects types settling (all other issues)

Each command should be of type Task -> Eff r a, possibly with a==() (otherwise dependent on Command and Command as a GADT.

• info
• build
• clean
• push
• pull

Note that pull is not a simple forM, and clean should not stop on failures. info is the easiest but is also merely informational, not truly required. push is the easiest operation.

For today, we only need the FROM, and maybe the list of steps (classified in how many RUN steps).

This can later become a big change, going away from plain docker files.

Data types:

• Path

Should support, at least, the following operations:

• read file
• write file (testing)
• mkdir (testing)
• list directory
• does directory exist
• find

And interpreters:

• IO interpreter
• pure stateful interpreter

In branch filesystem.

Let's you read in bits of a file at a time.

The current pull command searches the base image in all target images from the manifest (just like the bash script, the bug originated in the bash version). The correct way is to consider the order, such that the 1st image cannot be based on the 3rd.
Correct the command to

1. only consider earlier targets in the task list to decide whether not to pull
2. report an error if a task uses a base image which is target in a later task

Consists of reading and filtering the manifest file, and then issuing the required command.

• git rev-parse

Should support, at least, the following operations:

• docker rmi
• docker push
• docker build
• docker tag
• docker pull

Interpreters:

• Interpret into Proc effect.
• Interpret into Trace effect.

Requirements:

• retrieve current time (to form a timestamp)
• retrieve program name
• possibly: read environment variables

#39