Here is a list of common use cases that are addressed by GenoRing:
A small lab (with reduced budget)
It is a quite common story: a new project starts and is supported by main person which is often a PhD student, a post-doc, an intern or a short term contract. The project requires a website to have the data available to public. Setting up a website will take some time, especially if some application should be included (eg. a genome browser or a BLAST search). But once the person in charge leaves, the site is not maintained anymore. The website may be shut down for security reasons while its content may still be useful.
GenoRing purpose is to save time in the setup as well as in the maintenance. Since it provides an automated update system, it will extend the lifetime of the website and its tools. A non-expert should be able to maintain the site using the update command line.
Setting up a complete genome hub, a gene bank or a breeding site in short delays
GenoRing is designed to run such sites with few efforts. Since it is possible to select which module to enable, it becomes easy to build a genome hub, a gene bank site, a breeding site or a mix with few efforts.
Setup a non-containerized Drupal site
While GenoRing initially works with containerized applications, it can also be used to setup a complete website and then be turned into a local site run by a local web server and using a local database. The GenoRing platform would only be used to setup the site and then be removed... or kept just to use the auto-update feature.
Migrate an existing site to a new system
GenoRing provides features to integrate data "in place" from external sources such as existing databases, files or REST services. The site to migrate can remain in place and used while a GenoRing site is setup.
Provide a collaborative website for a project
Based on Drupal CMS, GenoRing supports access restriction as well as collaborative edition and comment features. Furthermore, it includes a built-in implementation for the plant Breeding API (BrAPI) and the Drupal JSON:API, a generic REST API that can be used to serve any kind of content. Some modules are also available to export data to central public repositories.