简体中文

OpenTrends is an open-source AI trend-reading app for following first-party information across technology, AI, product, finance, crypto, Chinese web platforms, and developer communities.

It is designed to track hundreds of primary sources, translate them into the reader's native language, and quickly summarize what changed so you can read global first-hand information without switching context across sites and languages.

• Curated topic pages designed for hundreds of first-party and official sources
• RSS, RSSHub, Hacker News, GitHub Trending, Reddit, Product Hunt, Zhihu, Juejin, NewsNow, Kickstarter, Crowd Supply, and Qwen Research adapters
• AI translation for reading source material in your native language
• Fast AI summaries that condense noisy source updates into a readable brief
• Cross-language topic pages for following global information flows without losing the original source context
• Source status endpoints and per-source refresh behavior
• Hot trend page caching through the runtime cache/KV layer plus in-memory request caching
• Docker Compose deployment for Postgres, RSSHub, API, migration, and web
• Void and Cloudflare/Alchemy deployment configs

opentrends/
├── apps/
│   ├── server/      # Hono API, trend adapters, source refresh, summaries
│   ├── web/         # TanStack Start frontend
│   └── fumadocs/    # Documentation app experiments
├── packages/
│   ├── api/         # oRPC router layer
│   ├── auth/        # Better Auth config
│   ├── config/      # Shared TypeScript config
│   ├── db/          # Drizzle schema, migrations, dev DB helpers
│   ├── env/         # Shared env validation
│   ├── infra/       # Cloudflare/Alchemy deployment entrypoint
│   └── ui/          # Shared shadcn/ui components and styles
└── docs/            # Design and implementation notes

• Bun 1.3.x
• Docker, for the local Postgres/RSSHub stack
• PostgreSQL, if you do not use Docker Compose

Install dependencies:

bun install

Create local env files from the examples:

cp apps/server/.env.example apps/server/.env.local
cp apps/web/.env.example apps/web/.env.local

Start Postgres and run the app:

bun run db:start
bun run dev

The API runs on http://localhost:3000. The web app runs on http://localhost:3001.

Server env is validated in apps/server/env.ts and packages/env/src/server.ts. At minimum, configure:

• DATABASE_URL
• BETTER_AUTH_SECRET
• BETTER_AUTH_URL
• CORS_ORIGIN

Optional trend and summary settings include:

• RSSHUB_BASE_URLS
• LLM_BASE_URL
• LLM_API_KEY
• LLM_MODEL
• TRENDS_REFRESH_SCHEDULER

Web env is validated in apps/web/env.ts. Configure:

• VITE_SERVER_URL
• VITE_SITE_URL

Trend pages use a short in-memory cache and the shared hot cache/KV abstraction in apps/server/src/trends/cache/hot-cache.ts. Source snapshots are stored through the source cache layer.

There is no checked-in bootstrap data cache. Runtime data should be generated by refresh jobs or requests and stored through the configured cache/storage backend.

bun run dev            # Start DB and all apps
bun run dev:web        # Start only the web app
bun run dev:server     # Start only the API
bun run db:start       # Start local database services
bun run db:migrate     # Apply Drizzle migrations
bun run db:generate    # Generate a Drizzle migration
bun run check-types    # Typecheck workspaces
bun test               # Run tests
bun run check          # Run Ultracite/Biome checks
bun run build          # Build workspaces

Copy the example Docker environment file and fill in BETTER_AUTH_SECRET:

cp .env.docker.example .env
perl -0pi -e "s|BETTER_AUTH_SECRET=|BETTER_AUTH_SECRET=$(openssl rand -base64 32)|" .env

For a public deployment, also replace the localhost values for BETTER_AUTH_URL, CORS_ORIGIN, VITE_SERVER_URL, and VITE_SITE_URL.

Start the full stack:

docker compose up -d --build

This starts Postgres, RSSHub, a migration job, the API server, and the web app.

The repository includes a GitHub Actions workflow that builds both Docker images and publishes them to GitHub Container Registry:

• ghcr.io/nexmoe/opentrends-server
• ghcr.io/nexmoe/opentrends-web

The workflow runs on pull requests, pushes to main, version tags such as v1.0.0, and manual dispatch. Pull requests build the images without pushing. Pushes to main publish main, latest, and sha-<commit> tags. Version tags publish the matching tag.

The published web image is built with these defaults:

• VITE_SERVER_URL=http://localhost:3000
• VITE_SITE_URL=http://localhost:3001

Set repository variables named VITE_SERVER_URL and VITE_SITE_URL before running the workflow if the image should be built for a public deployment URL.

Pull the published images:

docker pull ghcr.io/nexmoe/opentrends-server:latest
docker pull ghcr.io/nexmoe/opentrends-web:latest

To use the published images with Compose, override the server, migrate, and web image names in a separate file:

# docker-compose.ghcr.yml
services:
  migrate:
    image: ghcr.io/nexmoe/opentrends-server:latest
    build: !reset null

  server:
    image: ghcr.io/nexmoe/opentrends-server:latest
    build: !reset null

  web:
    image: ghcr.io/nexmoe/opentrends-web:latest
    build: !reset null

Then start the stack with the existing Compose file plus the override:

docker compose -f docker-compose.yml -f docker-compose.ghcr.yml up -d

This keeps the checked-in Postgres, RSSHub, migration, API, and web service configuration while replacing the locally built app images with GHCR images. Set the same environment variables documented in .env.docker.example.

Void deployment configs live in apps/server/void.json and apps/web/void.json. Deploy the API first, then deploy the web app with VITE_SERVER_URL pointing at the API origin.

Cloudflare/Alchemy deployment lives in packages/infra/alchemy.run.ts and uses secrets from the local environment or Alchemy secret env.

MIT