DeepSeek Harness Remote
DeepSeek Harness Remote: DeepSeek Harness 실행 PC와 모바일·PC를 안전하게 연결해 어디서나 작업 이어받기
ReboFiles는 자체 저장소에서 폴더·업로드·미리보기·버전·공유·휴지통을 지원하고, 워드 문서를 Rebodocs에서 연다
An open-source file manager for your app, on your own storage: folders, uploads, previews, versions, sharing and a trash, with Word documents opened in Rebodocs.
생산성TypeScript · RustGitHub @JFranciscoRobles온라인운영자 미확인
써 보셨어요? 한 번만 눌러 주세요. 로그인은 필요 없어요.
아직 감지된 업데이트가 없습니다. GitHub 릴리스가 나오면 여기에 보입니다.
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기메이커가 쓴 소개는 위의 한 줄이 전부입니다. 더 자세한 내용은 저장소 README에서 읽을 수 있습니다. 저장소 README ↗
README 전체를 불러오는 중입니다.
README 전문 보기 ↗ReboFiles is the drive of the Rebo suite, beside Rebodocs. The bytes go straight from the browser to your bucket and back, at addresses the server signs for a few minutes; the server keeps the entries (folders, names, owners, the trash, versions) in a store of your choosing, and asks your application who may do what.
It is early: every package is written and tested, nothing is on npm yet. Besides folders, versions and the trash: uploads in parts that resume, of whole folders, three at a time with the time each has left; the same file asked about before it goes; search by name and by what is written; a viewer; .zip downloads; links with a password or for one download; activity; quotas and a trash that empties itself; folder colours; settings; tools for an assistant; changes shown as they happen and folders of thousands, the drive read a piece at a time; comments; groups; pictures and text of PDFs made by the server; files checked by their bytes and by ClamAV; limits; retention, legal holds and a person's data exported; only the changed parts of a file sent; copies; requests for files through a link, each document in its place, accepted or returned from Received; shares that end; webhooks; frames of videos made by the server; Word versions compared; starred files; fields of your own on each entry; notifications in the drive; the space of each person for who looks after it; Excel workbooks shown and searched; pictures read with OCR; Google Cloud Storage and Azure besides S3; Word documents created, written by several at once and downloaded as PDF; and a desktop application that keeps a folder in sync. ROADMAP.md says what is next and what is checked.
// app/api/files/[...path]/route.ts, in Next.js
import { createDriveHandler, s3Storage, s3OptionsFrom, sqliteMetadata } from '@rebofiles/server';
const handle = createDriveHandler({
storage: s3Storage(s3OptionsFrom(process.env)),
metadata: await sqliteMetadata('drive.sqlite'),
identify: async (request) => (await session(request))?.user ?? null,
authorize: (user, action, entry) => true, // your rules
secret: process.env.REBOFILES_SECRET!,
base: '/api/files',
});
export { handle as GET, handle as POST, handle as PATCH, handle as DELETE, handle as PUT };
| Package | What it is | Runs in |
|---|---|---|
@rebofiles/core | The model of a drive: folders, names, moving, the trash, versions, search. | Anywhere, no DOM |
@rebofiles/server | The routes, authorize(), the bytes on S3 or the disk, the metadata in memory or SQLite. | Node 22.12+ |
@rebofiles/drive | The whole drive without a framework, mounted on an element, and the client of the routes. | Any browser |
@rebofiles/react | <FileDrive>, and the hooks it is built from. | React 18+ |
@rebofiles/mcp | Tools for an AI assistant, over HTTP or stdio, with the user's own rights; with Rebodocs, its Word documents edited, each change a version. | Node 22.12+ |
@rebofiles/sync | A folder of the disk kept as a folder of the drive, both ways; rebofiles-sync as a command. | Node 22.12+, or a desktop app |
apps/desktop is the drive in a window of its own, with Tauri, and a folder of the computer kept in sync from it. examples/ has the server in Next.js, Express, Hono and Fastify, and sign-in with Auth.js, Clerk or a token of your own, each run by its tests.
npm install
npm run dev # the playground, at http://localhost:5180: the drive on this computer, in storage/
npm run demo # the demo of the landing, at http://localhost:5181: entirely in the browser
npm run documents # Word documents made, written by several at once and read, at http://localhost:5184
npm run site # the landing page, at http://localhost:5182 (Next.js; npm run build:site makes it static, in apps/site/out,
# with the sitemap, llms.txt and a .md of each page, and fails on a page without its SEO)
npm test # Vitest
npm run test:browser # Playwright, in the Chrome of this computer
npm run typecheck # tsc, over every package
npm run lint # Biome
CONTRIBUTING.md has where things go, the conventions, and how a release is made. Every push and pull request runs the same in GitHub Actions.
MIT. Anyone may use it for anything.