Tool to automate running commands in docker.
Moby is a tool to automate running scripts in a docker container. This can be used to run tests or other stuff that depend on binaries or other stuff you don’t want to install.
Moby assumes there is a Dockerfile in the current directory. Currently there is no way to configure otherwise. So there should be a Dockerfile.
Create a file called moby.yml, this is the configuration file moby will search for. Example:
envlist: [test, build] test: before: push: - tests - tox.ini run: - apt-get install -y tox run: - tox build: run: - ./build.sh after: pull: - dist
Then run moby.
When the example is ran, moby builds and launches the container from the Dockerfile. The test environment is ran first. The tests directory and the tox.ini file are pushed to the running container (to the working dir). Then apt-get install -y tox is ran. Lastly, tox is executed. Then the build environment is ran. ./build.sh is executed and the dist directory is downloaded from the container to the current directory. After all this, the container is shut down.
An environment can have an after entry. This entry is considered an environment that is ran after the environment is ran.
An environment can have an after entry. This entry is considered an environment that is ran before the environment is ran.
envlist is a required entry, it states which environments are to be run.
An environment is created at the root with an arbitrary name. An environment only requires a run entry.
An environment can have a push entry. This states which files to push to the container.
An environment can have a pull entry. This states which files to pull from the container.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size moby-0.0.3-py3-none-any.whl (3.5 kB)||File type Wheel||Python version py3||Upload date||Hashes View hashes|
|Filename, size moby-0.0.3.tar.gz (2.8 kB)||File type Source||Python version None||Upload date||Hashes View hashes|