Access policy: Access from China is prohibited.
LMM Forge gives maintainers and contributors one accountable workflow for funded open-source work:
- publish a repository challenge with a defined scope, reward, delivery slots, and acceptance rules;
- accept funded work with a verifiable GitHub identity;
- attach Issue and pull request evidence to a delivery;
- review work and release escrowed rewards;
- preserve settlement, rating, tip, and dispute events in the same evidence trail.
The public challenge board is readable without an account. Signing in enables challenge acceptance and wallet funding. A new account receives permanent developer-console access after creating its first credential; no deposit is required for activation. Existing accounts and administrators retain their established access.
| Path | Role |
|---|---|
apps/web |
Shared React frontend and LMM Forge product experience |
apps/api-go |
Default production backend and bounty settlement implementation |
apps/api-rust |
Optional Rust preview backend and compatibility tooling |
The default production build compiles apps/web, synchronizes the verified assets into the Go embed tree, and then builds the Go service. The Rust backend remains opt-in and does not replace the default image or release path.
Review .env.example, replace all example credentials, and then start the default stack:
git clone https://github.com/LIghtJUNction/api.lmm.best.git
cd api.lmm.best
docker compose up -dOpen http://localhost:3000 and complete the setup flow. Common development commands are:
just setup
just dev
just test
just buildjust build produces independent frontend and Go backend artifacts in apps/web/dist and apps/api-go/out. PostgreSQL and Valkey are the default Compose services; the Go backend also retains its inherited SQLite and MySQL compatibility.
Before exposing a deployment:
- Enforce the access policy at the network edge in addition to displaying the notice in the application.
- Replace every example database, cache, and session secret.
- Terminate HTTPS at a trusted reverse proxy and configure exact trusted origins and proxy ranges.
- Keep PostgreSQL and Valkey on private networks and test database restoration.
- Review challenge escrow, wallet, rate-limit, logging, retention, and dispute settings.
Application copy is not a substitute for geographic enforcement. Operators are responsible for implementing and maintaining any required IP, account, payment, and legal controls.
LMM Forge is the product layer maintained in this repository. Its service foundation is derived from QuantumNous/New API, which builds on One API. The inherited New API compatibility layer, identifiers, copyright notices, and attribution remain intact.
For deployment and authentication details, see docs/authentication.md, NOTICE, and THIRD-PARTY-LICENSES.md.
This repository is licensed under the GNU Affero General Public License v3.0. Preserve the required QuantumNous/New API and One API notices, the visible upstream attribution, and all applicable third-party terms when redistributing a modified build.