Telegraph StorageTelegraph-Image

A considered Telegraph-Image workspace

Files should be reviewed before they are published.

Telegraph Storage turns this customized fork into one clear workflow: stage files in your browser, inspect them, then push them sequentially to the storage you already configured.

The dashboard uses the existing site sign-in when authentication is enabled.

Local first, remote when intended

A staging area, not an instant-upload trap.

Nothing is sent merely because it entered the workspace. Push is a deliberate boundary. If a request fails, the local item stays available for review and retry instead of disappearing into an optimistic success screen.

  1. 01

    Stage locally

    Add, drop, or paste files. Stable local copies remain on this device until you choose Push.

  2. 02

    Review in context

    Check MIME-aware previews, names, destinations, Albums, and the exact public output.

  3. 03

    Push sequentially

    One request runs at a time, with spacing, bounded retries, pause, cancel, and truthful progress.

  4. 04

    Manage remotely

    Search the remote index, organize Albums, and manage metadata or moderation without changing public object identities.

What the dashboard brings together

One place for the full object lifecycle.

01

Nested Albums

Group local and remote objects in a hierarchy. Moving or deleting an Album does not rewrite or delete its files.

02

MIME-aware previews

Images, video, audio, PDFs, and generic files receive appropriate surfaces rather than being treated as pictures.

04

Remote management

Browse paginated records, search and sort, rename display metadata, save, moderate, or remove index records.

About this fork

Built on Telegraph-Image, reorganized for deliberate storage work.

This repository retains the project’s upload, Telegram and R2 provider paths, public file serving, moderation, and management APIs. The customization focuses on a coherent landing page, sign-in, and authenticated workspace around those capabilities.