2c8a873e7286d797e88549d5a2825f0ea6fe3f04 chmalee Fri May 15 15:07:52 2026 -0700 HubSpace now allows tracks hubs to be defined via hub.txt+genomes.txt+trackDb.txt files, refs Baihe email and #37566 diff --git src/hg/htdocs/inc/hgMyData.html src/hg/htdocs/inc/hgMyData.html index 3279e43b9cb..6148d80ff1c 100755 --- src/hg/htdocs/inc/hgMyData.html +++ src/hg/htdocs/inc/hgMyData.html @@ -28,30 +28,40 @@ all files at once from your computer.
If a hub.txt file is not provided when uploading the data files, a hub.txt file is automatically generated. The generated hub.txt file is configured with the useOneFile trackDb setting, and as a result, each hub is limited to a single genome assembly.
+ Hub Space also accepts the standard multi-file hub layout: a hub.txt
+ that references a separate genomesFile (typically
+ genomes.txt), with one trackDb file per genome. Include
+ hub.txt, genomes.txt, every referenced trackDb, and any 2bit files
+ in the same upload, and Hub Space will derive each file's assembly
+ from the hub definition. For more complex multi-file hubs, the
+ hubtools
+ command-line uploader remains the recommended path.
+
Editing the generated hub.txt file is not yet supported. To customize the hub configuration or data display, replace the generated hub.txt file with your own version after uploading the data files.
By default, your most recently used genome assembly is selected after choosing which files to upload. Use the popular assemblies drop-down menu or the search box to select another genome assembly.