Labulubius Workspace

A personal web workspace with a KDE Breeze-inspired interface. The public pages organize links and reading sources; a Supabase-authenticated site administrator manages the directory, files, feeds, forums and a private note.

Pages

Route	Purpose	Data / access
/	Workspace home	Public
/nav	Website directory, search, favorites and categories	Published entries are public; administrators edit entries and icons in the UI (Supabase)
/news	FreshRSS-backed reader	Visitors can read the owner's selected, non-expired articles; administrators manage sources and categories
/forums	Discourse topic browser	Visitors see the selected public sources; administrators manage the shared directory
/drive	Private file manager	Administrator only; files live on the web server
/share	Public file/folder link manager	Administrator only; generated /f/<id> and /s/<id> links are public
/note	Private note	Administrator only; stored in Supabase
/about	Project overview	Public

nav.labulubius.com is rewritten to /nav by proxy.ts. The Drive subdomain redirects its page to the main-site UI, while its API remains on the web server.

Architecture

• Next.js 16 (App Router, React 19, TypeScript, Tailwind CSS 4) serves the UI. Supabase Auth and Row Level Security control administrator access. Navigator data, icons and the private note use Supabase; the navigator is managed in the UI, not in app/nav/sites.ts (which only defines types).
• The main UI is deployed to Vercel. The web machine also runs this Next.js application behind Nginx and Cloudflare Tunnel. drive.labulubius.com serves persistent Drive APIs and the server-side News/Forums relay target; feeds.labulubius.com serves generated authenticated RSS sources; share.labulubius.com serves Share APIs and public links. News and Forums requests from the Vercel UI go through same-origin /api/news and /api/forums before being relayed to web.
• Drive and Share files, News preferences and the Forums directory live outside Git on web. FreshRSS and its PostgreSQL database run in Docker there. Do not treat a Vercel deployment filesystem as persistent storage.

Local development

Requirements: Node.js 24 and npm, plus a Supabase project configured as described in supabase/README.md.

git clone git@github.com:labulubius/web.git
cd web
npm install

Create .env.local locally (never commit it) with your own project's values:

NEXT_PUBLIC_SUPABASE_URL=<your-supabase-url>
NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY=<your-publishable-key>
# Required to use local Drive and Share APIs; choose distinct absolute paths outside this checkout:
DRIVE_DATA_DIR=<absolute-private-drive-directory>
SHARE_DATA_DIR=<absolute-public-share-directory>

Run npm run dev and open http://localhost:3000. nav.localhost:3000 exercises the navigator host rewrite if your browser resolves that hostname. Login and database-backed features require a configured Supabase project and administrator account. News requires a reachable FreshRSS instance and API credentials on the server; see NEWS.md. The Share UI currently calls https://share.labulubius.com directly, so local development is not an isolated local Share backend without a code/configuration change.

npm run dev    # Development server
npm run lint       # ESLint
npm run typecheck  # TypeScript without emitting files
npm test           # Focused regression tests
npm run build      # Production build
npm run start  # Run the production build

Deployment and persistent data

Apply the SQL migrations and set up the administrator account using supabase/README.md. Set the two NEXT_PUBLIC_SUPABASE_* variables for both deployments (the publishable key is not a service-role secret). On web, configure distinct writable absolute DRIVE_DATA_DIR and SHARE_DATA_DIR paths outside the repository; do not set these directories on Vercel. Configure FreshRSS credentials for the web service separately; never expose them with NEXT_PUBLIC_ variables.

Build and run the Next.js service on web behind a reverse proxy, preserving the original Host header for host-specific behavior. Configure the Cloudflare Tunnel and DNS for the Drive, Feeds and Share hostnames, then deploy the main UI on Vercel. News and Forums API relays require a working drive.labulubius.com endpoint. Back up the server-side file directories, News preferences, Forums directory and FreshRSS data separately from Git and Supabase. The installed five-day News retention job and its operational checks are described in NEWS.md.

More details: DRIVE.md, SHARE.md, NEWS.md, FORUMS.md, operations and restore verification, supabase/README.md.

Repository map

• app/: pages, API routes, shared UI and server helpers.
• app/nav/: navigator UI and TypeScript types; actual entries are stored in Supabase.
• app/lib/: authorization, persistent storage, FreshRSS and Forums integration.
• proxy.ts: hostname-based route rewriting and Drive-page redirect.
• supabase/migrations/: database and storage policy migrations.
• scripts/: News retention SQL and hourly job.

License

No license has been specified for this repository.