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_DIRlocation on Windows:
HIFI_DATA_DIRlocation on OSX:
~/Library/Application Support/High Fidelity
HIFI_DATA_DIRlocation on Linux:
- Rolling backups now happen at the domain-server rather than the entity-server. These backups are in the
domain-server/backupsfolder. 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!