Define a source configuration model, credentials/certificate handling, connection lifecycle, loading/error states, and a shared file-browser UI over AsyncVFS. Taildrive sources should be derived from the running IPN peer list rather than configured as arbitrary URLs.
Support WebDAV mutation operations according to backend capabilities. Surface read-only or unsupported operations explicitly instead of hiding them.
Acceptance
configure and remove an arbitrary WebDAV source;
browse directories and read/download files;
upload and perform supported same-source file operations;
discover and browse permitted Taildrive shares;
source state survives navigation/reload without persisting plaintext secrets unsafely;
useful authentication, TLS, network, and VFS errors;
browser tests cover a local WebDAV server and a mocked or integration Taildrive source.
Depends on #28/#55 reaching a stable base. Cross-source operations are tracked separately.
## Goal
Add first-class remote filesystem sources to Tailshare:
- browse and read arbitrary WebDAV servers;
- upload, copy, move, rename, create, and delete content where the server permits it;
- discover Taildrive peers/shares and browse/read them through the same file UI.
This extracts the corresponding unchecked items from #28.
## Existing foundation
- WebDAV client/server and VFS: #22
- Taildrive WebDAV bridge and peer discovery: #27
- Tailshare application shell: #28
- SharedWorker/client consolidation: #55
## Scope
Define a source configuration model, credentials/certificate handling, connection lifecycle, loading/error states, and a shared file-browser UI over `AsyncVFS`. Taildrive sources should be derived from the running IPN peer list rather than configured as arbitrary URLs.
Support WebDAV mutation operations according to backend capabilities. Surface read-only or unsupported operations explicitly instead of hiding them.
## Acceptance
- configure and remove an arbitrary WebDAV source;
- browse directories and read/download files;
- upload and perform supported same-source file operations;
- discover and browse permitted Taildrive shares;
- source state survives navigation/reload without persisting plaintext secrets unsafely;
- useful authentication, TLS, network, and VFS errors;
- browser tests cover a local WebDAV server and a mocked or integration Taildrive source.
Depends on #28/#55 reaching a stable base. Cross-source operations are tracked separately.
codinget
added this to the Tailshare roadmap project 2026-07-12 02:58:16 +02:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Goal
Add first-class remote filesystem sources to Tailshare:
This extracts the corresponding unchecked items from #28.
Existing foundation
Scope
Define a source configuration model, credentials/certificate handling, connection lifecycle, loading/error states, and a shared file-browser UI over
AsyncVFS. Taildrive sources should be derived from the running IPN peer list rather than configured as arbitrary URLs.Support WebDAV mutation operations according to backend capabilities. Surface read-only or unsupported operations explicitly instead of hiding them.
Acceptance
Depends on #28/#55 reaching a stable base. Cross-source operations are tracked separately.