…icated

…d some pydantic api models

…ds login url path to base handler

…hild classes that don't need this functionality

…ookie created post login is used to retain login state.

…og_cli=false'

….py. Now run using 'python -m hydroshare_jupyter_sync'

…file. TODO: impliment config logic

…ented

…t of hsclient.json_models::ResourcePreview fields that have been subset

Current configuration parameters are `data` and `log`. Both are
directories. By default, hydroshare_juypter_sync looks for them at
~/.config/hydroshare_jupyter_sync/config and
~/.hydroshare_jupyter_sync_config in order. Meaning, if
~/.config/hydroshare_jupyter_sync/config is found first,
~/.hydroshare_jupyter_sync_config will not be read.

Data and log parameters can be specified in multiple ways.
1. Config files mentioned above using shell environment variable like
   semantics (i.e. DATA=/some/path).
2. As environment variables (i.e. export DATA=/some/path)
3. Using the CLI by passing a non-default configuration file
   (i.e. --config env_file).

…it greedily returns the firs that exists

…ection purposes

…ut post action.

The previous post action allowed for creation of a HS resource, for the
purpose of the minimum viable product this feature has been removed. In
the future this feature will be re-added.

… routing

…output

…name implies, it adds caching by overriding the resource method in the base class

…resources/files

… can download either files or folders

…ot contain ~ or ..

…o hydroshare

This handler assumes that a local version of a HydroShare
resource (does not have to be entire resource, could just be a file in a
resource) exists locally and is stored as it is canonically in
HydroShare (i.e. {resource_id}/data/contents/). Meaning that the local
file system mirrors the resource's file system structure on HydroShare.

The handler accepts one or more files via a json object ({"files":
[str]} in the request body using the POST HTTP verb. File names passed
in the json `files` array must be in the file system context of the
passed resource. They are specified relative to `/data/contents` or
`{data}/{resource_id}` (meaning, you can include `/data/contents` if
desired.) File paths passed outside {data}/{resource_id}/ ARE NOT
ALLOWED. Additionally, file path names cannot include `~` or `..`. A 403
Forbidden is returned in the response if they are passed.

Files are zipped relative to `/data/contents` (maintains directory
structure), uploaded to HydroShare, and unzipped. Files uploaded
overwrite existing files present on HydroShare. This operation cannot be
undone.

…d to change in the future. For now, it bypasses the redirect to /syncApi/login

…rigin set to localhost for cors support. Will likely need to change in the future

…ookie. This should reduce frontend login management complexity

… model

…header requirement and additions to ResourceMetadata api model

…not directory) path to the file's MD5 Hash. adds interfaces and concrete implimentations.

…nt and communicate the relationship between HydroShare resources', resource files, and resource MD5 Hashes.

…e FS map and allows for treating them as one FSMap

…e state of an AggregateFSResourceMap. Namely, are resources in/out of sync, only local/remote.

…ents are to be described as passed as an Enum

… observer, manage, and communicate local and remote hydroshare resources

…teardown process for resources that handle tracking, managing, and communicating the sync status of local and remote hydroshare resources that bookend a session.

…tem event handlers for observing a local hydroshare resource directory. Observations are used to update a LocalFSResourceMap instance and dispatching events used elsewhere in the application (i.e. file added).

…nc status between local and remote resources are pushed to the client across this websocket.

…truct as a singleton.

…ources. These events are now dispatched using an event system to update state elsewhere in application.

…server.py will be moved to the handlers subpackage.

…ill be completely removed in future. Currently functionality is retained in __init__.py of the handlers subpackage

…ndlers subpackage