Skip to content

progress.md

Latest commit

 

History

History
31 lines (26 loc) · 1.59 KB

progress.md

File metadata and controls

31 lines (26 loc) · 1.59 KB
Raw

FileDrop Progress

Status: Building

What's done

  • Node.js/Express backend: upload, gallery, download, share links, OIDC PKCE auth, anonymous management tokens, expiry, cleanup
  • Vanilla JS frontend: gallery, upload with progress, file preview (images/audio/video/PDF/text), OIDC login, owner actions
  • SQLite metadata store (PVC with sqlite storage class)
  • S3 storage (Bucket + Policy + S3User via s3.onyxia.sh CRDs)
  • OIDCClient (codemowers.cloud/v1) with PKCE, no client secret, ingressRef
  • Ingress with short hostname filedrop (expanded by platform admission)
  • Skaffold config validated (v4beta11, Kaniko cluster builder)

Access modes implemented

  • anonymous — anyone browses and uploads; management token shown once
  • upload-authenticated (default) — anyone browses; signed-in users upload
  • enforced-auth — sign-in required for everything

Known items to verify after deploy

  • S3 endpoint: http://minio.minio:9000 — update ConfigMap filedrop-config if incorrect
  • OIDCClient ingressRef requires passmower.ingressDiscovery.enabled; if not available, add explicit uri/redirectUris with expanded hostname
  • Actual public URL: read admitted Ingress after deployment

Files

  • src/index.js — Express app + all routes
  • src/db.js — SQLite setup
  • src/s3.js — S3 client (AWS SDK v3)
  • src/auth.js — OIDC discovery + JWT validation (jsonwebtoken + jwks-rsa)
  • public/index.html + public/app.js — SPA frontend
  • k8s/ — Bucket, Policy, S3User, OIDCClient, PVC, ConfigMap, Deployment, Service, Ingress
  • skaffold.yaml — Kaniko cluster build → zot registry