Git Integration

Catalyst Slate allows you to integrate with common Git providers and automatically deploy your applications. This enables seamless workflows and deployment management, enhancing developer productivity and deployment scalability to a greater extent.

The supported Git providers include:

You can deploy code built in any Node based client framework of your choice. Additionally, Slate provides native support for a wide range of frameworks as well. Refer to this help page to know the full list of supported frameworks.

We will now delve deeper into each deployment method in detail in the upcoming help sections.

Deploy from Private Repository

Catalyst Slate allows you to integrate with your Git accounts seamlessly, access your private repositories, and directly deploy applications from those repositories.

To deploy your web client application using the private repository integration method, please ensure to follow the below steps:

  1. Navigate to the Catalyst Slate service in the console and click Start Exploring.
slate-start-exploring
  1. Select your preferred Git provider to integrate with Slate.
slate-git-provider
  1. You will be redirected to Catalyst Settings->Git Integration. Click Add Account.
git-integration-settings
  1. Click Agree to accept the terms and conditions of the Git provider.
git-integration-agree

The Git account will now be integrated with Catalyst and listed here.

git-integration-successful

You can simply close this tab and navigate back to Slate. The integrated Git account and its list of repositories will be displayed here.

git-repository-linked
  1. You can click on the required repository to initiate a Slate deployment. In the Create Deployment pop-up, the repository name will automatically be considered as the application name as shown in the screenshot below.
create-deployment-popup
  1. Select the branch or commit of the repository that has to be deployed using Slate.
select-deployment-source
  1. Provide a name for your deployment.
enter-deployment-name
  1. Choose the front-end framework of your application using the drop-down menu.
choose-app-framework
  1. The Node runtime will be set to Node 18 by default. You can change it if required from the supported runtimes in the drop-down menu.
Note:
  • The Node.js runtime lets you run JavaScript code outside a web browser, like on a server or your computer. It helps you build websites and apps by giving JavaScript access to files, networks, and other system tools.

  • You should choose a runtime that matches the Node.js version your application is built with, as specified in your package.json file.

choose-node-runtime
Note: We now support **Node.js version 20** as well, which will be selected as the default option.
  1. Set the root path of your application.
Note: The root path (often written as "/") refers to the base directory where your client application's main files, including the source code, configuration files, and dependencies, are located.
set-root-path
  1. Enable Auto Deploy, so that any code pushed to the specific branch will get automatically deployed using Slate. This option is not applicable to commits. This step is optional.
enable-auto-deploy
  1. The output path, build command, and the start command will be auto-populated based on the detected framework. You can edit them, if required.
Note:
  • The output path is the directory where your application gets compiled or built for production.

  • The build command is the script that transforms your development code into production code.

  • The install command fetches and installs all dependencies required for your project. For example, the install commands for various client-side frameworks are:

    • React, Next.js, Vue, Angular, Sveltenpm install or yarn install
    • Astronpm install or pnpm install
    • Vitenpm install or yarn install
    • SolidJSnpm install or pnpm install
deploy-commands
  1. Set the required environment variables for the deployment, if required. This step is optional.
set-app-variables
  1. Click Deploy. You can click on Preview to view your live application. Click on View Deployment Summary for more details and configurations about the deployment.
deployment-summary-private

You can fetch the generated access URL of your application as shown in the screenshot below. You can edit the subdomain part of the URL by clicking on Edit URL.

edit-url-private

You can disable Auto-Deploy for this deployment by clicking on Change.

change-auto-deploy-private
  1. Enter the deployment name and click Disable.
confirm-disable-auto-deploy

You can sync the latest commit with the current deployment by clicking on the Sync Now button.

sync-now-button-private

You can also map the generated Slate URL with your custom domain if required.

You can view the list of deployments made to your application by switching to the History tab in the left pane. Refer to this help section to learn more about it. You can enable cache for your deployment by navigating to the Configuration tab in the left pane. You also have the option to configure environment variables required for your deployment, if required.

In the next section, we will discuss how to deploy an application directly from a public repository using Slate.

Last Updated 2025-07-07 22:11:41 +0530 +0530