FODI lists a OneDrive account from a static front end and a worker

A file browser with no server of its own

FODI stands for Fast OneDrive Index, and the README describes it as a OneDrive fast listing program that needs no server. That phrase needs unpacking, because there is no application server but there is definitely a backend. The repository is split into a front-end/ directory and a back-end-cf/ directory, so what you deploy is a static site plus a piece of serverless code, with the Cloudflare Worker doing the work of talking to Microsoft Graph on the browser's behalf. The listed features are compact. You can specify the path to display, you can encrypt a particular folder, deployment is free and needs no server, and there is basic preview for text, images, audio and video along with the three Office formats. The authors are also upfront about the drawbacks, listing that the feature set is simple and the interface rough, and that the Internet Explorer and UWP Edge browsers are not supported. There is a live demo linked, and the homepage field is empty, so the demo and the repository are the two places to look.

Deploying it in three ways, all on Cloudflare

There is a one click path and two others, and all of them end at Cloudflare Workers. The one click option uses the deploy to Cloudflare button, and the instructions are to visit your domain with the /deployfodi path appended. The note under it matters for updates: after updating the repository you have to fetch the kv_namespaces id from the Cloudflare dashboard and put it into wrangler.jsonc, so the configuration file is part of the deploy story rather than an afterthought. The second path is an online import, where you import the project into a private repository of your own on GitHub, edit wrangler.jsonc and commit, and then import that repository from the Cloudflare console. The third is a command line push, and the sequence is short:

git clone https://github.com/vcheckzen/FODI.git
cd FODI
# edit wrangler.jsonc, then
npm i wrangler
npm run deploy
# webdav config
npx wrangler secret put USERNAME
npx wrangler secret put PASSWORD

The last two lines are the WebDAV credentials, stored as Cloudflare secrets rather than in the repository, which is the right place for them. There is also an EdgeOne Pages option, with a button for deploying the front-end/ directory to that platform. The caution on the one click path is the one an adopter has to notice, and it is stated in both languages: supported only for personal accounts, use alternatives for other types of account, and creating your own app is recommended.

The token scheme is the whole access model

FODI does not ask you for a Microsoft password. It issues links, and the parameter documentation is the clearest description of the design. The path parameter is the front end starting directory, and the file parameter is the address of the file to download, in a form like /a/a.txt. The token is the access token, whose format is path,ts,te after an HMAC-SHA256. The ts parameter is optional and controls which permissions the token grants, with the list being download, refresh, list, upload, children and recursive, and when it is left out the default is download. The te parameter is the expiry date, formatted as a unix timestamp in seconds, and when it is left out the token never expires. The tb parameter is the starting directory for the token's effect and is used with the recursive permission. The format parameter converts the downloaded source file into another format. The worked example in the README shows the whole chain for a file at /Abc/a.txt with a password and an expiry timestamp, producing a URL with the token and the expiry and the format carried as query parameters, and the site computing that value for you from the password you set.

Encryption, WebDAV limits and the file size ceilings

The encryption section gives two ways to set the password, either by putting the sha256 hash of your password into a custom password file, or by setting the environment variable PASSWORD. That second option is what makes the token scheme work as a share link, since the same password that protects the listing also derives the token that authorizes a specific file. The WebDAV section has two operational details worth knowing before you enable it. Credentials are set as secrets named USERNAME and PASSWORD in the variables and secrets settings, and the upload limits are tied to the plan: 100MB on FreePlan, 200MB on BusinessPlan and 500MB on EnterprisePlan. Those are Cloudflare's own limits surfacing through the deployment, not choices FODI makes, so a larger file simply will not upload on a free plan. The download section adds two more options, with access through a PROXY_KEYWORD letting the worker act as a proxy, and a format query parameter on the file address letting you request a converted format, with the supported list linked to the Microsoft documentation on the drive item content format API.

Previews, and a development loop built on wrangler

The preview support covers pdf, markdown, images, audio and video, with two configuration paths. For local pdf preview you are told to download the PDF.js files from the mozilla repository, unpack them into a directory named pdfjs, comment out the fileOrigin !== viewerOrigin condition in viewer.mjs, and change the URL in the viewer.html file that points at the file. That is a manual integration rather than a configuration option, so it is worth knowing it exists before you promise a client a pdf preview. For markdown, the web page has an Optional Markdown extensions setting where you choose whether to enable GitHub alert styling and katex formatting. The development section is a pnpm install followed by editing wrangler.jsonc, then the type and dev scripts, which the package manifest shows as wrangler types for the worker type definitions, wrangler dev for the local server and wrangler deploy for the push. The update history in the README gives a sense of pace, with partial WebDAV support covering listing, upload, download, copy and move implemented on 2025.02.12, and upload support added on 2024.09.15.

Editorial conclusion

Adopt FODI when you want a quick browser based listing of a personal OneDrive account, with optional folder encryption, previews and WebDAV access, and you are willing to run it on Cloudflare Workers. Do not adopt it for a business or work Microsoft account, since the project states it is supported only for personal accounts, and do not treat it as a general purpose drive client, since the authors list the interface as simple and rough. Verify first that the token you generate carries the permissions you need, that the account type is one the project supports, and that you understand the token scheme carries an expiry before you share a link.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. README
4. vcheckzen/FODI on GitHub