Enviroments workflow

Unity Services
, ,
3

Hi,
This can vary based on the scale of the team and personal philosophy, but here’s the take I recommend

Best practices are:

  1. Keep everything under version control, this allows you to have PRs and diffs
    remote config can be treated as regular assets (see this post ).
  2. You should have at least 3 environemnts, Production, Staging and Dev
  • Production should be restricted and only used by experts or live-ops
  • Staging contains only versions of the service content that you’re comfortable with
  • Dev should be up to date with whatever is in your main branch
  1. Only devs that are actively tweaking service setup should have their own environments. The rest should be using “Dev”.
  2. You can use the UGS CLI to push from branch “main” to your “dev” environment. Ideally this is automated and ran on CI on merge
  3. Promotions can be done via CLI or deployment window, by having a stable branch and then “deploying” to the staging environment.
  4. Reconciling LiveOps (direct dashboard) work with local work can be done with a UGS CLI “fetch”. This turns dashboard setup into local configuration files understood by the Unity Editor and the UGS CLI