Skip to content

[Meta] GenoRing Roadmap #32

@guignonv

Description

@guignonv

To be completed and sorted...

Work done:

  • Single command line to generate config, install the system and start GenoRing
  • Basic Drupal auto-update through Docker compose restart
  • GenoRing module API with
    • hook support (start/stop, init/enable/disable/uninstall, backup/restore, update/upgrade,...)
    • module interactions
    • dependencies support
    • profile support (frontend/backend)
    • no, single, and multiple docker container support
  • Local or alternative service versions support
  • Basic backup support
  • Metadata support (saved in dedicated files, used in directory structure)
  • Dashboard
  • Multiple and parallel GenoRing instances support on a same server
  • Back-end mode support
  • File permission support through a local Linux user/group
  • Support for non-exposed volumes (file system)
  • Local Docker container image building support
  • Windows operating system support
  • Full system reset support
  • GenoRing Drupal module
  • GenoRing Drupal theme
  • GenoRing Drupal distribution
  • GenoRing Drupal project scaffold
  • JBrowse module
  • Gigwa module
  • BrAPI Mapper module
  • Simplified container interactive shell access
  • ARM architecture support
  • Main GenoRing documentation (about, installation)
  • Developer documentation
  • Module development template
  • Installation diagnostic

Next tasks:

  • Automate metadata filling (inherit from parent element, default values, etc.)
  • Document metadata use
  • Allow to enable multiple modules with their dependencies all at once in the start command line
  • Handle Drupal auto-update through the web interface or cron
  • Provide a GenoRing core update system (based on config with a github API link)
  • Provide a GenoRing module search and update interface
  • Improve offline/installation support: display a basic page when system is installing or is (partially) offline
  • Automated tests for GenoRing core
  • Implement Tripal tasks to manage how program execution should be handled
  • Chado loading through Tripal
  • GenoRing theme with custom image and predefined layouts
  • Data model aggregator implementation
  • Galaxy module
  • Genoboo module
  • Gigwa Drupal module with authentication
  • Document and recommend the use of WSL on Windows (because of file system issues)

Future plans:

  • Ontology browser
  • Taxonomy browser
  • SSL support (https)
  • Predefined user profile (for collaboration)
  • Anti-spam support
  • Basic anti-DDOS support
  • Clouflare optional integration (as a module?)
  • Predefined content types (projects, tools, institutes, teams,...)
  • JBrowse 2 module
  • Merge GenoRing JBrowse Drupal sub-module with Tripal JBrowse
  • JSON API use documentation

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions