Changes to location of entity server data file (models.json.gz)


With Beta Release 65 you can now download, upload, and create content archives from within your domain server settings page. To support this, one of the changes we made was to synchronize the entity server’s entities back to the domain server, enabling:

  • Proper support for entities in a distributed server setup. If you move your entity server to another machine, it will automatically pick up the latest entity data from the domain server. Previously you needed to do this manually.
  • Entity file (models.json.gz) updates being centralized at the domain server, making backup and recovery simpler.
  • Rolling backups that contain all of your content - entities, assets, and domain content settings.

If you didn’t know about the models.json.gz, or if you never touched it, everything will be the same for you. If not, there are a few changes you should know about:

  • Your models.json.gz is still in the same place on the entities server.
  • Your models.json.gz is now synchronized back to the domain server, inside of your HIFI_DATA_DIR/domain-server/entities folder.
  • HIFI_DATA_DIR location on Windows: %APP_DATA%\Roaming\High Fidelity
  • HIFI_DATA_DIR location on OSX: ~/Library/Application Support/High Fidelity
  • HIFI_DATA_DIR location on Linux: ~/.local/share/High Fidelity
  • Rolling backups now happen at the domain-server rather than the entity-server. These backups are in the domain-server/backups folder. Because assets are generally large, we don’t store the assets inside of each backup. Instead, you can get a backup with all of the associated assets through the domain-server web interface.
  • Directly replacing the models.json.gz in your domain-server or entities directories will not always work because of the synchronization process. The preferred method is to use the domain-server web interface. If you would like to update the models.json.gz file manually, you will need to delete the models.json.gz on your entity server (inside of assignment-client/entities) and replace the models.json.gz on your domain server (inside of domain-server/entities).

If you have any questions, please don’t hesitate to ask!



Why are these files partly .zip. And partly. .gz ? I’m a winrar person and had to go discover 7zip to mess with the gz bit


Can we already me all high fidelity files away from the C: drive where things like this not belong, to other drive like D: Is there config option ?


Because using .gz would have meant introducing another unfamiliar file type for Windows users (tarballs), and because we had already used zip archives in other locations, we decided to stick with .zip. Our expectation is that most users won’t want or need to inspect these files, but hopefully this makes these files easier to deal with for those who do, even if the internal models.json.gz file still requires a third party utility to open them.


We don’t provide a way to specify the location of the backups right now, but it’s something that is on our list of future improvements.


kinda what i was saying why not have them all zips?supose it dosent actually matter tho lol


Because we already rely on models.json being gzipped in so many places it would be a significant amount of effort to change, but I agree that the mismatch is unfortunate.

closed #8

This topic was automatically closed after 30 days. New replies are no longer allowed.