How casbin/casnode works
Project type and purpose
• This is a full‑stack, open‑source forum and social Q&A platform (“Casnode”), implemented as a Go backend + React frontend.
• Its key features include user authentication (Casdoor integration), content posting and moderation, search, notifications, file uploads, localization, and a Swagger‑powered public API.
File structure
Top‑level divisions:
• Backend (Go):
– main.go, controllers/, routers/, object/ (domain objects + business logic), service/ (external integrations: mail, OSS, tokenizer), conf/, util/, casdoor/, discuzx/ (adapters)
– swagger/ (API docs), Dockerfile, docker-compose.yml
• Frontend (React):
– web/src/ (components, CSS, i18n, admin & main pages, backend API wrappers), web/public/, package.json, craco.config.js
• Config & CI:
– conf/app.conf, .github/workflows/, go.mod/go.sum
README for additional insights
• Describes Casnode as an alternative to StackOverflow & Flarum, powered by ChatGPT and integrating with Casdoor for SSO.
• References Docker deployment, public API (Swagger), installation docs.
Main components and their interactions
a. Components
1. User’s browser (React SPA)
2. Go HTTP server (REST + SSR endpoints)
3. Database (e.g., MySQL/PostgreSQL)
4. Casdoor (external OAuth/AuthN service)
5. External storage (OSS)
6. Mail service (SMTP)
7. Cron jobs (object/cron.go)
8. Swagger UI (API docs)
b. Interactions
– Browser ←→ Go server: REST calls (JSON) for sign‑in, posts, search, notifications; SSR (via routers/filter_ssr.go) for initial page render.
– Go server ←→ Database: CRUD operations via object/*.go layer.
– Go server ←→ Casdoor: user authentication, user data sync (casdoor/adapter.go, discuzx/casdoor_init.go).
– Go server ←→ OSS: file uploads/downloads (service/oss.go).
– Go server ←→ Mail: email notifications (service/mail.go).
– Go server ←→ Cron: scheduled tasks like notifications cleanup or mailing list (object/cron.go).
– Swagger UI serves from swagger/ directory to document public APIs.
Architectural patterns and design principles
• Layered architecture (presentation → controllers → routers → service/domain → persistence)
• Adapter pattern for integrating Casdoor and DiscuzX (casdoor/, discuzx/)
• Separation of concerns: controllers handle HTTP, object layer holds business logic, service layer for external calls, util for logging/JSON/path.
• MVC‑like: routers dispatch to controllers; controllers orchestrate object methods; object methods call data stores.