If you do not have git LFS set up, it may be in your interest to have these images hosted on some type of cloud storage, so that pulling the repo locally isn't cumbersome.
To add support for pushing images to cloud storage, we provide a postprocessor.
It provides various data stores (and utilities to manage them) for "knowledge posts", with a particular focus on notebooks (R Markdown and Jupyter / IPython Notebook) to better promote reproducible research.
Check out this Medium Post for the inspiration for the project.
Is the Knowledge Repository missing something else that you would like to see? A knowledge repository is a virtual filesystem (such as a git repository or database).
A Git Knowledge Repository, for example, has the following structure: # The git repository metadata .resources # A folder into which the knowledge_repo repository is checked out (as a git submodule) - .knowledge_repo_# Local configuration for this knowledge repository - Then, all users and servers associated with this repository will be updated to the new version.
If the database does not exist, it is created (if that is possible) and initialised.We would love to work with you to create the best knowledge repository software possible.If you have ideas or would like to have your own code included, add an issue or pull request and we will review it.Note that the web application can live on top of multiple Knowledge Repo backends.Supported types so far are: There are two different ways to do this, depending on whether your organization already has a knowledge data repository or not: If your organization already has a knowledge data repository setup, check it out onto your computer as you normally would; for example: will allow you to update it to be a knowledge data repository.
Note: The Knowledge Repository is a work in progress.