Our genomes.config file is getting a bit out of control and is quite difficult to manage since we have so many genomes in there.
Taking a leaf out of the linux config structure - how would you feel about creating a genomes.d folder into which you could place any number of .config files. You could then split your configuration between these (eg one per assembly, one per species - whatever you liked) and the configuration would be read from all of them. You could leave the original genomes.config in place so this wouldn't break anything for existing setups but would give some more flexibility as the scale of some of the installs started to increase.
A suggestion (and an offer to actually code it!)
Our
genomes.config
file is getting a bit out of control and is quite difficult to manage since we have so many genomes in there.Taking a leaf out of the linux config structure - how would you feel about creating a
genomes.d
folder into which you could place any number of.config
files. You could then split your configuration between these (eg one per assembly, one per species - whatever you liked) and the configuration would be read from all of them. You could leave the originalgenomes.config
in place so this wouldn't break anything for existing setups but would give some more flexibility as the scale of some of the installs started to increase.