Application environments


Deploy App

All your application has two environments: development and production.

By default, every application created starts in development environment. Production environment is available once you deploy your application.

Several pages in the Portal provide a Development/Production toggle switch (only if you deployed application to production) for areas where it's useful to be able to view Development or Production data as you continue to develop your game.

Ideally you would want to develop your game in Development, deploy to Production at some point when you are ready, and then continue to develop new features of game in Development again.

Development environment

Development environment is state of application with features that are currently in development. This mode provides developers with the possibility to develop game with ServerBytes, apply changes and test them without affecting players.

Production environment

Production environment is the tested version of your application that you want to provide to your users.

Deploying application to production

At any point during development when you are happy with the state of your game, you might want to create a version of the application that you want to deploy to run in production. Open the application details page, and click on Deploy button.

Deploying the application disconnects all users and copies plugins and configuration data from development to production environment.

Deploying application to production is a permanent action. After the deployment is done your application will run in production environment unless is deleted.

Dialog will open and you have to choose method for migration your data from development to production. Please read the options carefully as some may result in irreversible data loss.

When application is deploying, plugin web interfaces will be disabled so you won't be able to open plugin web interfaces until application is deployed.

When production environment of your application is different than development change icon will be visible next to deploy button.

Configuration migration strategy

You can choose one of four available migration strategy:

  1. Skip migration

    No data is copied.

  2. Migrate configuration

    Configuration is copied from development to production environment.
    Entries with same id are not updated.

    When data is copied to production, new entries from development are copied to production environment, however entries with ids in production environment that matches ids in application development environment are not updated.

  3. Migrate and overwrite configuration

    Configuration is copied from development to production environment.
    Entries with same id are overwritten.

    When data is copied to production, new entries from development are copied to production mode, while entries with ids in production environment that matches ids in application development mode are overwritten.

    Since the production entries are overwritten this may lead to data loss on production environment.

  4. Snapshot migration

    Configuration is copied from development to production environment.
    Existing configuration on production environment is deleted.

    Snapshot migration ensures that the production environment is an exact replica of the development.

    Since only development entries are copied to production and production entries are deleted this may lead to data loss on production environment.

Configuration between the development and production environment is separated. You can make changes to development environment, but production mode will not be affected. This allows you to work on the next version of your game and make update to the game and test it before you deploy to production again. If you are working on a significant update, you might be in a position where your development configuration is very different to your production configuration.

If there is an urgent fix that needs to be applied to the production, or you want to change plugin configuration you can do this directly on production without disrupting work on development features.

What's next Learn more about plugins next.

results matching ""

    No results matching ""