browse-everything
browse-everything copied to clipboard
samvera
Rails engine providing access to files in cloud storage
Currently, attempting to use `yarn lint` within `.internal_test_app` for the build fails errors related to React compatibility issues with Hooks. A work-around is currently offered in the `README`.
This should draw heavily from https://rubygems.org/gems/dropbox_api
This should draw from either the NPM registry or GitHub in order to import React Components or Web Components for the user interface in 2.0.0.
It is not at all clear that one needs to install `karma` in order to run the JavaScript tests. Should one *not* have the `karma` CLI tool available globally, one...
This is currently breaking on release 1.0.2
Currently, this process is a bit more complex, and most of this relies upon the user having some basic familiarity with https://console.developers.google.com/. The process of managing applications and credentials for...
Part of the rationale behind https://github.com/samvera/browse-everything/issues/297 was that standardized [Web Components](https://github.com/w3c/webcomponents/) could be introduced into lightweight user interfaces for BrowseEverything. Using StencilJS, Web Components themselves can be loaded using a...
This should draw heavily upon https://rubygems.org/gems/aws-sdk-s3
This is going to be necessary for the 2.0.0 release, and I'm uncertain as to whether or not we should continue to use https://rubygems.org/gems/ruby-box (as its last stable release was...