Deployments Configuration

To automate the process of building and delivering applications AppMaster.io has an extensive deployment mechanism. You can create multiple deployment plans to separate development, pre-production and production branches. Every plan has a deployment target for server binary and mobile applications.

Backend Deploy Targets

Every Backend Deploy Target has its own configuration options and tradeoffs.

Backend Deploy Target

Description

Required configuration

AppMaster Cloud Services

The default target for any new deployment plan. Backend deployed to the selected data center, managed by AppMaster.io

  • Select region for deployment

Amazon Web Services

Deploy backend binary to Amazon EC2 server.

  • Running EC2 server instance

  • Running PostgreSQL compatible database

  • SSH credentials

Google Cloud Services

Deploy backend binary to Google Cloud Services Compute Engine.

  • Running Compute Engine instance

  • Running PostgreSQL compatible database

  • SSH credentials

Microsoft Azure

Deploy backend binary to Microsoft Azure VM.

  • Running Azure VM instance

  • Running PostgreSQL compatible database

  • SSH credentials

Custom Linux Server

Deploy backend binary to your custom Linux server.

  • Running PostgreSQL compatible database

  • SSH credentials

Build only

Only generates binary for the specific operating system and CPU architecture.

  • Select OS and CPU Architecture

Mobile Applications Deploy Targets

Mobile App Deploy Target

Description

Required configuration

AppMaster.io Developer App

AppMaster.io Developer application was published at AppStore and Play Market to let you work with your application without publishing your own.

None

Apple AppStore (IOS only)

Apple AppStore publication process.

  • Apple ID with a developer account

Google Play Market (Android only)

Google Play Market publication process.

  • Google Developers Console credentials