A personal browser homepage for fast bookmark access across browsers with instant search.
- Set your browser homepage as https://homepage.hsichen.dev.
- Press Space to start searching, and Enter to open.
- Sign in to upload a wallpaper; guests keep the default mountain scene.
- Click the location control to sync the nearest Taiwan weather and AQI station.
After combining this with HandyTab, opening any tabs feels like a breeze.
Core features work without an account. Location is requested only after clicking the location control. The selected Taiwan location is stored in a same-site cookie for SSR and mirrored in browser storage with weather/AQI caches. Guest bookmarks stay in browser local storage; signed-in bookmarks sync to PostgreSQL under the Clerk account. Wallpaper sync requires sign-in and uses private, authenticated object storage.
Requires Node.js 22+ and Bun.
git clone https://github.com/Hsiii/homepage.git
cd homepage
bun i
bun dev- Runtime: Bun, Next.js 16 App Router, React 19, TypeScript, Turbopack in dev, Node.js standalone server in production.
- SSR: Hydrates location, weather, AQI, Clerk state, and signed-in wallpaper.
- Auth: Clerk auth
- Storage: Standard PostgreSQL for bookmarks and wallpaper metadata; local files in development, Cloudflare R2 in production, and Vercel Blob as a migration-only compatibility provider.
- External data: OpenWeatherMap or Open-Meteo for weather; Taiwan MOENV for AQI.
Production runs on the Oracle VM behind Caddy. Every push to main publishes
ghcr.io/hsiii/homepage for Linux AMD64 and ARM64. Dependencies and standalone
output are built inside the target Linux image, so production never receives
native modules from the development Mac.
Changes reach main through a pull request. Deploy from a clean local main
that matches origin/main; the command waits for that commit's image and asks
the Oracle platform to pull it. It never pushes code:
bun run deployThe container listens on 0.0.0.0:3102 and exposes /api/health for health
checks.
Schema changes are tracked in migrations/ and never run from an application
request. Set DATABASE_URL to any PostgreSQL connection string, then apply and
verify migrations before starting the application:
bun run db:migrate
bun run db:verifyLocal wallpaper files are selected with
WALLPAPER_STORAGE_PROVIDER=local and default to .data/wallpapers. Production
uses WALLPAPER_STORAGE_PROVIDER=r2 with a private bucket and an R2 API token
scoped to object read/write for that bucket. Configure R2_ENDPOINT, R2_BUCKET,
R2_ACCESS_KEY_ID, and R2_SECRET_ACCESS_KEY; do not put their values in Git.
During migration, WALLPAPER_STORAGE_PROVIDER=vercel-blob remains supported with
the existing Blob token. Metadata is read through provider-neutral object keys,
so the database is ready for copying objects to R2 and switching the provider.
The non-destructive copy, byte-level verification, cutover, and rollback process
is documented in the persistence migration runbook.