The pip install requires that you have pandoc and pandoc-citeref installed. A NAtive install with pip has the advantage that it may be much faster than for example an instalation in a virtual machine via vagrant or a container.
However, these instalation methods may be much easier as you do not have toinstall that dependencies yourself.
The image for bookmanager is available at
To pull the premade image please use
docker pull cloudmesh/bookmanager:latest
Now you can list the images with
docker image list
to run a shell in a container that includes bookmanager, please use
docker run -v `pwd`:/cm -w /cm --rm -it cloudmesh/bookmanager /bin/bash
In that shell you can call bookmanager
See the next section and execute the commands we give in the Makefile targets while completing the variables accordingly. You can also install make via choco and use the Makefile.
We ar looking a Windows user that can contribute a bat file or a packaged .exe, or give us the example command for docker
Here the preparation steps:
mkdir cm
cd cm
git clone https://github.com/cyberaide/bookmanager.git
cd bookmanager
make image
Now you can use that image to create books. We will explain here a more advanced example
TODO: give an example here while compiling our cloud computing book
https://github.com/cloudmesh-community/book.git make cm
This will log you into the container that alsoo has the cm volume mounted in /cm now you can use the bookmanager in cm while using the content that you have in your native OS.
In the container you need to do the following:
/cm# cd book
/cm/book# cd books/cd 516-sp20/
:/cm/book/books/516-sp20# time make proceedings
The output is in /cm/pub/docs
in teh container or the pub
folder on
your native OS that you previously created.
To show you the performance differences on this more complex example I copied some information from my computer:
Mode | time on Gregor's macOS |
---|---|
Native | 34.948s |
Container with mount of cm in host system | 48.782s |
Container with locally checked out book folder | 40.372s |