Join the Agent Deck Discord Server!
Discord에서 Agent Deck 커뮤니티 확인, 357명과 자유 음성·텍스트 채팅 이용
개인 계정의 공개 저장소 소유자는 GitHub로 로그인해 운영자를 확인하고 소개를 직접 관리할 수 있습니다. 관리자 승인은 필요하지 않습니다.
로그인한 뒤 확인 파일을 만들어 이 저장소의 기본 브랜치에 30분 안에 커밋해 주세요. 다른 브랜치나 포크의 파일은 인정하지 않습니다. 파일을 올린 뒤 아래에서 확인하면 관리자 승인 없이 관리할 수 있습니다. 자격을 유지하려면 파일을 남겨 두세요.
로그인이 필요하면 로그인 화면으로 이동합니다. 로그인 후 이곳으로 돌아와 원하는 확인 버튼을 다시 눌러 주세요.
프로젝트 폴더에서 /nomorevibe verify를 실행하면 소유권을 확인하고 소개를 직접 관리할 수 있습니다.
1분 만에 확인하기Multiforum is a platform that supports forums with extra features, such as an event calendar, a wiki, and the ability to share downloads such as video game mods.
저장소 README에서 가져옴
README 전체를 불러오는 중입니다. 아래는 저장된 발췌입니다.
Start a usable local instance, including Neo4j, the backend, the frontend, and
an automatically provisioned administrator:
Then open http://localhost:3000 and sign in with the
default local password multiforum-local-admin. No Auth0, cloud storage, maps,
email provider, or manual Cypher bootstrap is required. See the
local self-hosting quick-start before
customizing credentials or exposing any service beyond your machine.
Multiforum is a community platform that lets people create and manage topic-based forums with multiple content types:README 전문 보기 ↗Start a usable local instance, including Neo4j, the backend, the frontend, and an automatically provisioned administrator:
docker compose up
Then open http://localhost:3000 and sign in with the
default local password multiforum-local-admin. No Auth0, cloud storage, maps,
email provider, or manual Cypher bootstrap is required. See the
local self-hosting quick-start before
customizing credentials or exposing any service beyond your machine.
Multiforum is a community platform that lets people create and manage topic-based forums with multiple content types:
Key differentiators:
Docs: https://docs.multiforum.net/ Website: https://www.multiforum.net/ Hosted Demo: https://www.topical.space/
Multiforum is split across two repositories:
The frontend talks to the backend exclusively through GraphQL.
Backend architecture: the data model, GraphQL schema, and resolver design are documented in depth in the backend's architecture overview and the references linked from it. This README and the frontend architecture doc cover the frontend and the cross-tier auth flow; for anything about how data is stored, related, and queried, start with the backend docs.
These are the main technologies and, more importantly, why they fit a cross-posting, deeply-interconnected community platform. If you have never used them, the short version of each explains what problem it solves here.
Nuxt is a framework on top of Vue that adds server-side rendering (SSR) — the first version of a page is built on the server and sent as ready-to-read HTML, then "hydrated" into a live app in the browser. That matters here for three reasons:
Nuxt's file-based routing also maps cleanly onto the many nested routes a forum
app needs (/forums/[forumId]/discussions/[discussionId], etc.).
Multiforum's data is fundamentally a graph, not a stack of independent tables. A single discussion can be cross-posted into many forums; comments nest arbitrarily deep; users connect to forums through roles; moderation issues link content, actions, and suspensions together. In a relational database, "show me every forum this download appears in" or "walk this comment thread" turns into a pile of join tables and recursive queries.
Neo4j stores data as nodes and relationships directly, so those traversals — follow the edges between connected things — are natural and efficient. The shape of the database mirrors the shape of the product.
Because the data is a graph, the API is too. GraphQL lets the frontend ask for exactly the connected data a screen needs — a discussion with its channels, author, and comment counts — in a single request shaped like the result. Apollo Client adds a normalized cache so repeated views of the same entity stay consistent and fast without manual bookkeeping.
Auth0 is a managed authentication provider. Rather than building and securing our own login, password reset, and social/single-sign-on flows, we delegate that to Auth0 and focus on the product. It pairs with the SSR auth-hint strategy above to keep login state correct across server and client.
Start here:
Architecture:
Feature areas and plans:
All developer docs are indexed in docs/README.md.
Hosted documentation: docs.multiforum.net.
This project is in active development.