Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

WIP: Topic/abstract storage #144

Merged
merged 35 commits into from
Mar 17, 2020
Merged

WIP: Topic/abstract storage #144

merged 35 commits into from
Mar 17, 2020

Conversation

breezykermo
Copy link
Member

@breezykermo breezykermo commented Mar 14, 2020

closes #124

This started as a PR to abstract out what mtriage uses to store media during runtime as an abstract storage layer, so that it could write media either to the local disk or to a remote storage such as S3. It has ended up as a serious rewrite of almost all internals.

  • write conceptual description of abstract storage.
  • write conceptual description of more robust etype implementation.
    • including support for custom etypes in lib/etypes
  • detail refreshed docs/tutorial structure
  • API for 'user-defined' functions changed to receive and return specific types.
  • using pathlib for internal paths
  • docs and tutorials have become much better structured, will submit another PR for this.

@breezykermo breezykermo merged commit 6ff3b0e into master Mar 17, 2020
@breezykermo breezykermo deleted the topic/abstract-storage branch March 17, 2020 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Allow chaining analysers at runtime through YAML
1 participant