legumeinfo/gcv: v2.3.0

This release fixes some bugs, updates dependencies, and introduces a handful of new features. Notably, all files related to Docker Compose have been moved to a separate, independently versioned repository: legumeinfo/gcv-docker-compose.

Major features:

• Default parameter values can now be set from the config file (see the Wiki for details)
• Instructions page screenshots now support responsive image sizing and each image has a lightbox for closer inspection (see the Wiki for details)
• A scale-screenshot command has been added to the NPM package CLI to allow admins to generate scaled copies of screenshots to support responsive sizing in production
• "Advanced" chromosome genes and chromosome length parameters have been added to the macro-synteny parameters to allow users to only generate blocks for chromosomes that have a minimum number of genes and/or a minimum physical length (bp), respectively

Minor features:

• The macro-synteny distance metric now uses multiset Jaccard instead of regular Jaccard
• Distance is now the default macro-synteny ordering scheme used when one isn't specified
• The Redis loader is now a service in the microservices Docker Compose files, though it is not automatically run with Docker Compose up
• Multiple alignments no longer contain empty columns
• The micro-synteny gene family legend now emits the names of the genes in a family via the broadcast channel when a family in the legend is hovered over
• The togglable orphans gene family feature from v1 of GCV was reimplemented
• The GCV path (base href) can now be set in Docker via the GCV_PATH environment variable in the production container

Bug fixes:

• Updated the RediSearch heath check to prevent microservices from starting before the database is loaded
• Automatic Redis snapshots are now disabled since our access pattern is write once, read many, which fixes a bulk loading bug
• Added the node_modules/ directory as a volume in the development container
• Changing the micro-synteny search parameters now actually triggers a new search instead of just clearing the view
• Resizing a viewer's container no longer resets the container's scroll position