Skip to content

Claude/folder content organization db6i6o#439

Open
bbaranoff wants to merge 5 commits into
caiiiycuk:8.xxfrom
bbaranoff:claude/folder-content-organization-db6i6o
Open

Claude/folder content organization db6i6o#439
bbaranoff wants to merge 5 commits into
caiiiycuk:8.xxfrom
bbaranoff:claude/folder-content-organization-db6i6o

Conversation

@bbaranoff

Copy link
Copy Markdown

No description provided.

claude and others added 5 commits July 6, 2026 22:20
Walks a source directory, detects each DOS game folder (a folder holding
a .exe/.com/.bat), and writes a ready-to-run <name>.jsdos bundle for each
one into a single destination folder. Each bundle is a ZIP with the game
files at the root and a generated .jsdos/dosbox.conf whose [autoexec]
launches the game's main executable.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QsuXbx5DKP5Mf6WnuoHHN5
Package DOS game folders into ready-to-run js-dos (.jsdos) bundles in the
cloud instead of running a script locally. The Worker serves a drag-and-drop
folder-upload page and a POST /bundle endpoint that zips the uploaded files
(fflate, no Node built-ins) with a generated .jsdos/dosbox.conf whose
[autoexec] launches the auto-detected main executable.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QsuXbx5DKP5Mf6WnuoHHN5
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QsuXbx5DKP5Mf6WnuoHHN5
…on-db6i6o

Add script to package DOS games into js-dos bundles
…ndles

Drop DOS game folders under dos/ and they are packaged into ready-to-run
.jsdos bundles at deploy time and served by the Worker:

- dos/README.md documents the drop-a-folder workflow
- worker/scripts/build-bundles.mjs scans dos/* and writes public/games/*.jsdos
  plus a games.json index (bundles are build output, gitignored)
- worker/src/jsdos.mjs holds the shared bundling logic (conf template,
  executable auto-detection, zip) used by both the build and the upload path
- the Worker serves the bundles via a static-assets binding, lists them on /,
  and keeps the ad-hoc folder upload at /upload
- README documents Cloudflare Workers Builds settings (root directory = worker)
  so Git deploys don't try to install the whole app at the repo root
- sync worker package-lock with package.json (wrangler, workers-types)

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01QsuXbx5DKP5Mf6WnuoHHN5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants