Workspace and Storage

Overview

All data files are stored directly on your local file system in a root Workspace folder - keeping your work private and safe even if the app is uninstalled or browser site data is cleared. Only user account and subscription-related details are stored on cloud servers. The Workspace structural hierarchy is as follows:

The Workspace folder is assigned during initial setup and can be changed at any time from the Dashboard Settings.

Instance & Access Constraints

• Single-Instance Lock:

  To prevent data corruption, the application locks the Workspace folder so only one application instance can access it at a time. Running multiple instances connected to the same Workspace folder is not supported.

• Sequential Multi-User Access:

  Multiple users can share access to the same Workspace folder only if access is strictly sequential. The application does not support concurrent access.

File System Access API

The application uses the browser's native File System Access (FSA) API to read and write Workspace files.

Folder Handles & Permissions

• Directory Selection:

  During initial setup, you select a local Workspace directory. The application caches this folder handle in IndexedDB so it is persisted for all future access.

• Permissions:

  The application operates within the browser's secure sandbox and requests read and write access for the selected folder during setup. Browsers may prompt for re-authorization on subsequent launches. To eliminate repeated prompts, grant permanent folder permissions in site settings or install the application as a desktop app.

• Security Boundary:

  Access is strictly restricted to the chosen Workspace folder and its subdirectories. The application cannot read or access any other files on your file system without explicit consent.

Multi-Device Access via Cloud Drives

You can transfer and access your Workspace across multiple devices using cloud storage services (such as Google Drive, Microsoft OneDrive, Dropbox, or iCloud Drive) as a manual storage location.

Manual Sync Workflow

1. Copy Workspace to cloud on primary device (Device A):

   When you finish editing on Device A, copy your local Workspace folder into your cloud drive (e.g., OneDrive/Logiop Workspace) and allow the cloud client to complete the sync.

2. Download to local disk on secondary device (Device B):

   On Device B, copy or download the OneDrive/Logiop Workspace folder to a dedicated local directory on your hard drive.

3. Select local directory in Logiop Studio:

   Run Logiop Studio on Device B, select the downloaded local Workspace directory during setup, and grant browser permissions via the File System Access API.

Multi-Device Access via Git

Using Git version control with hosting providers such as GitHub, GitLab, or Bitbucket is the recommended multi-device strategy for developers. It gives you complete version history, branching capabilities, and explicit control over when updates are pushed and pulled across devices.

Step-by-Step Configuration

1. Initialize and push from primary device (Device A):

   Open your terminal, navigate to your local Workspace folder on Device A, initialize a Git repository, and push it to GitHub:

   cd /path/to/your/Logiop-Workspace
   git init
   git add .
   git commit -m "Initial workspace commit"
   git branch -M main
   git remote add origin \
     https://github.com/your-username/your-workspace-repo.git
   git push -u origin main

2. Clone repository on secondary device (Device B):

   On Device B, clone the repository from GitHub to a local directory:

   cd /path/to/desired/local-folder
   git clone https://github.com/your-username/your-workspace-repo.git
   cd your-workspace-repo

3. Select cloned local directory in Logiop Studio:

   Run Logiop Studio on Device B, choose the cloned local folder during setup, and grant browser permissions.

4. Daily sync routine (Push & Pull):

   Before starting work on any device, pull the latest changes:

   git pull origin main

   When you want to save your progress to remote, commit and push:

   git add .
   git commit -m "Updated state machines and project files"
   git push origin main

Backups & Workspace Reassignment

You can create compressed Workspace backups, restore a Workspace, and reassign your active Workspace folder from the Dashboard.