You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Oct 19, 2026. It is now read-only.
Repository navigation
Commit 41ca003
Browse filesBrowse the repository at this point in the historyBrowse files
refactor: migrate to ceres application/transport paths and centralize HTTP errors (#2139)
* refactor: enforce DTO boundaries and extract jupiter-migrate for faster builds
Move mono HTTP DTOs into ceres/model (admin, webhook, bot, note, group) and
route label/group logic through MonoApiService facades so mono no longer
imports jupiter::model. Add CI guard for the DTO boundary, document the
three-layer model rules in ceres/README, and relocate ProtocolError HTTP
mapping to mono.
Extract SeaORM migrations into jupiter-migrate with optional jupiter/migrate
feature gating, fold context into mono/bootstrap, and slim common by
removing axum. Update mono routers, storage init, and workspace deps
accordingly.
* update docs
* refactor: thin mono routers with MonoAppServices facades and ceres domain modules
Introduce MonoAppServices and TransportContext so mono routers stop calling
storage directly, and split MonoApiService into domain modules (user, issue,
conversation, code review, gpg, note, reviewer, cl_list, etc.). Move
notification dispatch/triggers and webhook admin/delivery into ceres
application, relocate pack helpers to infra, and extend CI guards for
callisto, jupiter::service, transport/application, and router storage access.
* refactor: migrate to ceres application/transport paths and centralize HTTP errors
Deprecate ceres legacy re-exports (api_service, pack, protocol, build_trigger,
code_edit) and switch mono/ceres call sites to application::* and transport::*.
Add typed MegaError variants with shared HTTP status mapping in common, simplify
mono ApiError, and improve Git SSH protocol error handling.
Further thin group/tag/artifacts routers via MonoApiService facades and extend
CI guards to block legacy ceres import paths in mono.
Copy file name to clipboardExpand all lines: README.md
+6Lines changed: 6 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -53,6 +53,12 @@ Mega is evolving toward deeper AI-native capabilities:
53
53
54
54
To facilitate a rapid deployment and hands-on experience with the Mega service, the following instructions are derived from the project's [documentation](https://github.com/web3infra-foundation/mega/tree/main/docker).
| Storage assembly |`jupiter/model`| Bundles of `callisto` entities from storage/services; no serde/utoipa |`jupiter` storage/service, `ceres` application only |
45
+
46
+
Rules:
47
+
48
+
-`mono` routers must **not**`use jupiter::model` — map via `ceres::model` and `MonoApiService` facades.
49
+
-`mono/src` must **not**`use callisto::` or `jupiter::service::` — storage entities and service calls stay in `ceres` application layer.
50
+
-`ceres/src/transport` must **not** reference `MonoApiService` (transport ↔ application boundary).
51
+
-`api-model` is **not** mono HTTP schema (except shared wrappers like `CommonPage` / `Pagination`).
52
+
-`ceres/model` is the mapping hub: `impl From<jupiter::model::*>` and `impl From<callisto::*>` live here.
53
+
-`application/build_trigger/model` is a ceres subdomain API schema (build triggers); same HTTP rules as `ceres/model`, kept alongside orchestration until a later consolidation.
0 commit comments