Skip to main content

Managing the Local Datastore

Your local changes to a Git-enabled application live in the browser's local datastore until you push them. The Datastore controls let you export that data to a file, import it back, and clear it — the recovery path behind most of the Git troubleshooting steps in this section.

The datastore is designed for advanced troubleshooting and data handling. In normal work you never need it: commit and push instead.

warning

The local datastore is specific to one browser on one machine. It is not a backup, it is not shared with your team, and clearing it removes local work that has not been pushed. Export before you clear.

Before you begin​

Push or commit anything you want to keep. Exporting produces a file you can re-import, but pushing to the remote is the only way to make work available to your team or on another machine.

Opening the Datastore​

  1. Select Settings in the left sidebar.
  2. Select Git Settings.
  3. Select the Datastore tab.
  4. Select Open Datastore.

Koodisi also offers Open Local Data Store directly from the Cannot find HEAD error, which is the most common reason to come here.

Exporting​

Select Export datastore. Koodisi exports all data from the datastore and saves it locally as a serialized JSON file.

Do this before clearing the datastore, before re-cloning an application, and before any Git operation you are unsure about — it is the only way back to local work that was never pushed.

Importing​

  1. Select Import Datastore File.
  2. Drop a JSON file onto Upload a JSON file, or select it.
  3. Select Import.
warning

Importing overwrites all existing datastore data, and the process cannot be reversed. Export the current datastore first if it holds anything you have not pushed.

Clearing​

Clearing permanently removes all local datastore data. It is not reversible, and unpushed work is lost.

  1. Select Clear Datastore.
  2. Confirm at the Delete Datastore? prompt.

The page reloads once the datastore is cleared. Re-clone your applications from the remote repository afterwards. See Cloning Git Applications.

How you know it worked​

An export downloads a JSON file. An import or a clear reloads the page, and your application list reflects the new state — after a clear, Git-enabled applications show as missing from local storage until you clone them again.

When it does not work​

SymptomCauseWhat to do
An application shows Application missing from local storage after clearingExpected. The datastore no longer holds a local copy.Select Clone My Application in the Version Control panel, or clone it again.
The import file is rejectedThe file is not JSON, or exceeds the size limit.Import a file produced by Export datastore, unmodified.
Local work is missing after an importThe import replaced the datastore rather than merging into it.Import the export you took before the change. If none exists, the work is recoverable only from the remote.