In this folder you have to insert the Dockerfile with defined build args to customize and automate the build. If you want to add a new tool you just have to create a folder for that specific tool inside the tools directory. README.md (optional README for Docker Hub).Those are all tools that do not have an official Docker Image provided by the developer: NameĮvery tool in the tools directory contains at least two file: This is the current list of tools that have been added. Whether build or not if an image with the same tagname has been found Whether check against Docker Hub instead of local Docker before build If you want to quickly add a new tool folder starting from one of the available templates you can run this command: If you want to know the available tools you can run this command: Since the tests parameter has been added to the configuration structure of the tool is can be helpful to test if the inserted commands do return a 0 status code. Tool_name MUST be the name of the directory inside the tools folder. In this mode RAUDI tries to build only the specified tool. In this mode RAUDI tries to build all the tools if needed. For this reason we advice you to add it! You can also create a personal access token without any scope since anything we do is read some info for every GitHub repo. For unauthenticated users GitHub allows up to 60 requests per hour, while authenticated users are allowed up to 15.000 requests per hour. env.sample file) and add your GitHub Personal Access Token to avoid Rate Limiting. Before using it locally you should create a. There are different options that can be used when running it. RAUDI can build and push all the tools that are put into the tools directory.
#Linux exiftool scrub install#
To run the test you need to install pytest with the command pip install pytest (it is not in requirements.txt since it is needed only for testing purposes) and then you may run: The setup phase is pretty straightforward, you just need the following commands: Here is the documentation for working with BuildX: The requirements to be met are the following: That’s all guys: go to Action, enable it for your forked repo, wait until midnight, and the Workflow will do the heavy work!