All Collections
Portal Pages
Design | Core App Info | Admin Tools
Design | Core App Info | Admin Tools
Jason Liang avatar
Written by Jason Liang
Updated over a week ago

Admin Tools provide specialized utilities for managing the brainCloud configuration, It is very useful during development, and for propagating configuration updates into production.

To view and edit your preferences, go to the Admin Tools page on the dashboard.

Deployment

Understanding the deployment options

  • [x] Do not overwrite product/pricing information - Keep this checked if you have set up separate In-app purchase items for production vs. development. Uncheck otherwise.

  • [x] Do not overwrite push notification certifications - Similarly, check this if you have separate push certificates for production vs. development. Uncheck otherwise.

  • [x] Do not overwrite integrations - Keep this checked if you have separate integration settings for production vs. development.

  • [x] Do not overwrite My Servers configurations - Prevents the deployment for changes in the settings for your external and/or hosted servers. This is important if you have hosted servers. Since your configurations (minimum # servers, server sizes, etc) for production will likely be very different than development

  • [x] Do not overwrite lobby configurations - Prevents development lobby settings from overwriting the production values.

  • [x] Do not overwrite Item Catalog - Keep this checked if you have separate Item Catalog definitions for production vs. development.

  • [x] Do not overwrite Leaderboard, Tournaments, etc. configurations - Prevents development Leaderboard, Tournaments, etc. configurations from overwriting the production values.

  • [x] Do not delete independent Leaderboards not present in source app - Prevents the independent leaderboards from deleting when the previous above option, [x] Do not overwrite Leaderboard, Tournaments, etc. configurations, is unselected.

Choose a new app that you want it to be deployed with all the configuration data and custom files of the current app from the drop-down menu. Click Deploy button, you will see a pop-up confirmation box, confirm by entering the app name, and click Deploy button on the dialogue box to continue. Once done, you will see your new app deployed with the same configurations and custom files as source one, from cloud code to statistics rules, app logo to platform setting. 

Note, if choose an existed app, all configuration of the selected app will be overwritten by the configuration data of the current app.
Also note, the config for Cloud Code-My Servers Settings is not imported. 

Checkpoints

A checkpoint is created in the progress of both Deploy and Import Configuration Data operations, recording only those collections having data. And on the Restore Checkpoint (or Import Configuration Data), all data for data access objects having scope GAME_CONFIGURATION will be deleted, except for collections containing history.

Note for Checkpoints:

  • The scripts and leaderboard configs that created thereafter the checkpoint will not be deleted when restoring to that checkpoint. 

  • "Checkpoints" include the application's metadata - but does not save or restore files (i.e. legacy global files and new global files are excluded).

Configuration Data

The configuration Data section applies the same mechanism as Deploy, but only for configuration data, that means no custom files will be transferred. You can keep the app configuration data which is a .bcconfig file as a record locally.  

Custom Files

This section is used for import/export custom files, you can go to Custom Config | Files to check the result after your import operation. You can keep the app custom files data which is a .bcfiles file as a record locally.

Application Cache

Clear Cache will flush such as the script cache, leaderboard cache, and custom entity cache for the current app.

Data Deletion

This section gives users convenient access to delete users with one click.
Note, you may still find users profile IDs from User Monitoring | User Summary, but those users cannot be selected once deleted.

Did this answer your question?