Skip to main content

App Advanced Settings

Our App page has a tab called Settings. In this tab you can find the following advanced settings:

Switching Deployment Method​

You can switch between CLI and GitHub deployment methods directly from the App Settings UI.

From CLI to GitHub​

If your app is currently deployed via CLI and you want to connect it to a GitHub repository:

  1. Go to your App's Settings tab
  2. Under Deployment Method, click Switch to GitHub
  3. Follow the prompts to connect your GitHub repository
  4. All environments will be updated to use the default branch from your repository

After connecting, you can configure each environment's branch in its respective Settings tab.

From GitHub to CLI​

If your app is connected to GitHub and you want to switch to CLI deployment:

  1. Go to your App's Settings tab
  2. Under the GitHub repository information, click Disconnect GitHub - Switch to CLI
  3. Confirm the disconnection

After disconnecting, future deploys will need to be done via the CLI or GitHub Actions.

Note: You can always reconnect to GitHub later if needed by following the "From CLI to GitHub" steps above.

Sticky Sessions​

You should enable Sticky Sessions in your App settings when you want to keep the same client connecting to the same container.

This depends a lot on your stack, for example, if your server keep state of the connected client it's probably a good idea to enable Sticky Sessions.

Now if your app is stateless, like a REST API, you probably don't need Sticky Sessions.

Without Sticky Sessions enabled your connections will be more balanced across all the containers so just use it if you really need it.

Blue/green deployment​

You should enable Blue/green deployment in most cases as you want to have zero downtime deployments.

Blue/green deployments are going to make your old containers alive while new containers are not passing the health check.

Make sure you customize your health check so your new containers are only going to be ready when your app is really ready to accept new requests.

Block communication from other accounts​

You should enable Block communication from other accounts in most cases as you want to restrict your app env to only accept connections from our Ingress and maybe from other app envs in your account.

This is a security measure to avoid your app env to be exposed to other containers running in our clusters that don't belong to your account.

If you run multiple accounts where your containers talk to each other across accounts then you should disable this option, so you can connect your app envs between accounts.