If you are having problems, be sure all your files and the directories are publicly accessible. You may also wish to reset the browser occasionally to clear all existing data. For hubs to work, your server must also accept byte-ranges. You can check using the following command to verify "Accept-Ranges: bytes" displays:
curl -I http://yourURL/hub.txtNow that you have the assembly hub copied from above, you can copy the directory and start to edit some of the documents such as genomes.txt, groups.txt, and trackDb.txt to understand how they work. Refer to the Assembly Hub User Guide to understand how to build a twoBit file for your own original fasta files. Read more about trackDb settings in the definition document.
+Assembly hubs also support chromAlias and chromAuthority, which let the Browser map chromosome names
+across different naming schemes and display a preferred convention. A default naming scheme can be
+set using the chromAuthority setting.
+
This assembly hub is a an abbreviated version of a larger plant assembly Public Hub. You can explore the larger hub structure here.
Please note that the Browser waits 5 minutes before checking for any changes to these files.
When editing hub.txt, genomes.txt, trackDb.txt, and related hub files, shorten this delay by
adding udcTimeout=1 to your URL. For more information, please see the
Debugging and Updating Track Hubs section of
the Track Hub User Guide. Also, for more detailed
instructions on setting up a regular hub, please see the Setting Up Your Own Track Hub section of the Track Hub User Guide.
By running gfServers from your institution, you can enable blat on your assembly hubs. See