ClusterWare User Guide
  • 👋Welcome to ClusterWare!
  • Learning Path
    • 🔭Overview
    • 1️⃣Create a distributed NodeJS application in 10 minutes
      • Step 1: Create a new cluster
      • Step 2: Onboard servers to ClusterWare
      • Step 3: Install server software
      • Step 4: Create application instances
      • Step 5: Import application source code
      • Step 6: Start the application
      • Step 7: Create and start application load balancer
    • 2️⃣Uniformly secure access to your infrastructure
      • Step 1: Create Security Policy
      • Step 2: Install Firewall
      • Step 3: Apply Security Policies
    • 3️⃣Secure the data in-transit with SSL
      • Step 1: Gateway Security
      • Step 2: Endpoints Security
    • 4️⃣Eliminate a single point of failure in 10 minutes
      • Step 1: Onboard a new server
      • Step 2: Install Niginx
      • Step 3: Configure DNS
      • Step 4: Create and start the failover load balancer
      • Step 5: Run a load balancer outage experiment
  • Fundamentals
    • 🧩Sync, Insights, Tasks
    • 🤖Supported Technologies
    • 🛡️Server Authentication Methods
    • 💡Connectivity Troubleshooting
  • Services
    • Clusters
      • Cluster Selection & Creation
      • Editing Cluster
      • Notification Subscriptions
      • Auto-deployment (CI/CD)
    • Dashboard
      • Load Balancers & Applications
    • Servers
      • Create/Edit Server
      • Status
      • Software
      • Security
        • Enabling Non-Root Firewall Status Checking
        • Changing Firewall Status
        • Applying Security Policies
      • Metrics
      • Alerts
    • Applications
      • Create/Edit Application
      • Status
      • Git
      • Output Log / Error Log
      • Metrics
      • Alerts
    • Load Balancing
      • Create/Edit Load Balancer
      • Status
      • Gateway Security
      • Endpoint Security
    • Security Policies
      • Create/Edit Security Policy
Powered by GitBook
On this page
  • Overview
  • Key Sections
  • Repository URL
  • Status
  • Current Branch
  • Local Branches
  • Remote Branches
  • Sync Actions
  • Initializing new repository (Cloning)
  1. Services
  2. Applications

Git

PreviousStatusNextOutput Log / Error Log

Last updated 11 months ago

Overview

This interface allows users to manage and synchronize their application code repositories directly within the ClusterWare Console.

Key Sections

Repository URL

The URL of the Git repository for the application. The repository URL is set in the cluster settings and is used primarily for Git clone operation upon initialization of the application on the server.

Status

Indicates if the working directory is clean.

  • Clean: The working directory doesn't include any untracked changes in files.

  • Not clean: There are differences between the latest commit in local repository and your filesystem. It may happen when installing dependencies alters the package.json file or when your application modifies files within the repository at runtime.

Keeping the working directory clean ensures that builds are reproducible. It allows the build process to reliably generate the same output from the same commit. By not storing state in the working directory, developers ensure that every checkout of the repository is consistent and free of environment-specific data.

To restore the repository to the initial state use the Clean button.

Current Branch

Displays the current branch checked out in the local repository.

Options

  • Change branch: Click on the current branch dropdown and select a different branch.

  • Pull: Click on the Pull button to update your local repository with latest changes in the remote repository. Git pull modifies the local working directory.

Local Branches

Lists the local branches available in the repository. The latest commit hash is shown along with the most recent commit message.

Remote Branches

Shows the remote branches and with the same commit hash and message is displayed.

Options

  • Fetch: Allows to fetch the latest updates from the remote repository. Git fetch does not modify local working directory.

Sync Actions

  • Status: Syncs information displayed in all sections of this tab: the current Git status, local branches and remote branches.

Initializing new repository (Cloning)

If ClusterWare detects that the directory specified in the application config is not a Git repository, it asks the user to initialize it.

The following steps work for public and private repositories.

  1. Open your repository settings in a separate browser tab and allow list the SSH key provided in Public Key section to read the repository data.

  2. Click Clone to initialize the local repository and pull latest changes from the default remote branch

The following steps work for public repositories not requiring authentication to read the repository data.

  1. Click Clone to initialize the local repository and pull latest changes from the default remote branch