Update README with info on new approach.
Chris Pressey
3 years ago
7 | 7 | felt not-quite-right somehow, so this repository was created to hold all |
8 | 8 | the Dockerfiles, build scripts, and documentation for each Docker image. |
9 | 9 | |
10 | It is rather experimental. It may turn out that a different way of | |
11 | organizing all this would be better. We'll see. | |
10 | In addition -- and this is significant -- there is a set of driver | |
11 | scripts in the `bin` directory of this repository, which run the | |
12 | executables in these containers almost as if you had the executable | |
13 | installed on the host. | |
14 | ||
15 | Each driver script will download any image it needs from Docker hub | |
16 | first, if it is not yet present on the system. | |
17 | ||
18 | So all you need to do is put `bin` on your executable search path, | |
19 | and suddenly you have a myriad of Cat's Eye Technologies' tools and | |
20 | language interpreters and such at your disposal, right from your | |
21 | command line (or shell, or Terminal, or whatever you like to call it.) | |
22 | ||
23 | There are some caveats of course. See the README of the | |
24 | [containerized-hastec][] project for more information on this approach. | |
12 | 25 | |
13 | 26 | [Cat's Eye Technologies]: https://catseye.tc/ |
14 | 27 | [Docker images available on Docker Hub]: https://hub.docker.com/u/catseye |
28 | [containerized-hastec]: https://github.com/catseye/containerized-hastec/ |