Vítor Vasconcellos
79d8e2871a
* Handle RPC errors when adding Locations - Add custom error codes for NeedRelink and AddLibraryToMetadata errors in backend - Handle errors in AddLocationDialog form - Show custom error message for above errors and ask user to confirm action - Handle user action confirmation with appropriate RPC method (`locations.relink`/`locations.addLibrary`) * Abstract openDirectoryPickerDialog logic to a function - Add 'Unkown Error' when code doesn't match a know one * Fix bugs in logic to handle `locations.create` errors - Fix minor issue: AddLocationButton opened the dialog in desktop even when the user cancelled the file picker - Replace ternary with object for custom form error messages to allow for easier expansion - Break onSubmit logic up into functions - Remove incorrect `locations.indexer_rules.delete` call - Fix Checkbox element state not updating on external form state changes * Adjust AddLocationDialog style to match other Dialogs in the app - Reset exception code at the end of `confirmAfterError` * Rework how backend errors are handled when adding Locations - Change NeedRelink and AddLibraryToMetadata errors to use 409 (Conflict) status code and a static message. - Only enable custom submit logic in AddLocationDialog for 409 (Conflict) errors that have a known custom error form message. - Differentiate previous errors based on their messages instead of status code in AddLocationDialog onSubmit. - Add @hookform/error-message dependency for improved form validation error rendering. * Invalidate library.list to ensure it is shown on sidebar * Improvements to AddLocationDialog - Remove uncessary scope block and make useEffect depend directly on `form` - Move `form.handleSubmit` from `onSubmit` call to `handleSubmit` definition - Change basic Checkbox to RadixCheckbox and adapt onChange logic to onCheckedChange - Some simple styling improvements to the error message
Spacedrive
A file explorer from the future.
spacedrive.com »
Download for
macOS
·
Windows
·
Linux
·
iOS
·
watchOS
·
Android
~ Links will be added once a release is available. ~
NOTE: Spacedrive is under active development, most of the listed features are still experimental and subject to change.
Organize files across many devices in one place. From cloud services to offline hard drives, Spacedrive combines the storage capacity and processing power of your devices into one personal distributed cloud, that is both secure and intuitive to use.
For independent creatives, hoarders and those that want to own their digital footprint, Spacedrive provides a free file management experience like no other.
What is a VDFS?
A VDFS (virtual distributed filesystem) is a filesystem designed to work across a variety of storage layers. With a uniform API to manipulate and access content across many devices, VDFS is not restricted to a single machine. It achieves this by maintaining a virtual index of all storage locations, synchronizing the database between clients in realtime. This implementation also uses CAS (Content-addressable storage) to uniquely identify files, while keeping record of logical file paths relative to the storage locations.
The first implementation of a VDFS can be found in this UC Berkeley paper by Haoyuan Li. This paper describes its use for cloud computing, however the underlying concepts can be translated to open consumer software.
Motivation
Many of us have multiple cloud accounts, drives that aren’t backed up and data at risk of loss. We depend on cloud services like Google Photos and iCloud, but are locked in with limited capacity and almost zero interoperability between services and operating systems. Photo albums shouldn’t be stuck in a device ecosystem, or harvested for advertising data. They should be OS agnostic, permanent and personally owned. Data we create is our legacy, that will long outlive us—open source technology is the only way to ensure we retain absolute control over the data that defines our lives, at unlimited scale.
Roadmap
View a list of our planned features here: spacedrive.com/roadmap
Developer Guide
Please refer to the contributing guide for how to install Spacedrive from sources.
Architecture
This project is using what I'm calling the "PRRTT" stack (Prisma, Rust, React, TypeScript, Tauri).
- Prisma on the front-end? 🤯 Made possible thanks to prisma-client-rust, developed by Brendonovich. Gives us access to the powerful migration CLI in development, along with the Prisma syntax for our schema. The application bundles with the Prisma query engine and codegen for a beautiful Rust API. Our lightweight migration runner is custom built for a desktop app context.
- Tauri allows us to create a pure Rust native OS webview, without the overhead of your average Electron app. This brings the bundle size and average memory usage down dramatically. It also contributes to a more native feel, especially on macOS due to Safari's close integration with the OS.
- We also use rspc which allows us to define functions in Rust and call them on the Typescript frontend in a completely typesafe manner, so no unnecessary bugs make it into production!
- The core (
sdcore) is written in pure Rust.
Monorepo structure:
Apps:
desktop: A Tauri app.mobile: A React Native app.web: A React webapp.landing: A React app using Vite SSR & Vite pages.
Core:
core: The Rust core, referred to internally assdcore. Contains filesystem, database and networking logic. Can be deployed in a variety of host applications.
Packages:
client: A TypeScript client library to handle dataflow via RPC between UI and the Rust core.ui: A React Shared component library.interface: The complete user interface in React (used by appsdesktop,webandlanding)config:eslintconfigurations (includeseslint-config-next,eslint-config-prettierand alltsconfig.jsonconfigs used throughout the monorepo.macos: A Swift Native binary for MacOS system extensions.ios: A Swift Native binary (planned).windows: A C# Native binary (planned).android: A Kotlin Native binary (planned).