|
1 | 1 | <div align="center"> |
2 | | - <img alt="Click to see the source" height="200" src="https://devsh-graphics-programming.github.io/Nabla-Asset-Manifests/auxiliary/nabla-glow.svg" width="200" /> |
| 2 | + <img alt="Click to see the source" height="200" src="https://devsh-graphics-programming.github.io/Nabla-Asset-Module/auxiliary/nabla-glow.svg" width="200" /> |
3 | 3 | </div> |
4 | 4 |
|
5 | 5 | <p align="center"> |
6 | | - <a href="https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Manifests/actions/workflows/smoke.yml"> |
7 | | - <img src="https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Manifests/actions/workflows/smoke.yml/badge.svg" alt="Smoke Status" /></a> |
8 | | - <a href="https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Manifests"> |
9 | | - <img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fdevsh-graphics-programming.github.io%2FNabla-Asset-Manifests%2Fmetrics%2Frepo-size.json" alt="Repository size" /></a> |
| 6 | + <a href="https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Module/actions/workflows/smoke.yml"> |
| 7 | + <img src="https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Module/actions/workflows/smoke.yml/badge.svg" alt="Smoke Status" /></a> |
| 8 | + <a href="https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Module"> |
| 9 | + <img src="https://img.shields.io/endpoint?url=https%3A%2F%2Fdevsh-graphics-programming.github.io%2FNabla-Asset-Module%2Fmetrics%2Frepo-size.json" alt="Repository size" /></a> |
10 | 10 | <a href="https://opensource.org/licenses/Apache-2.0"> |
11 | 11 | <img src="https://img.shields.io/badge/license-Apache%202.0-blue" alt="License: Apache 2.0" /></a> |
12 | 12 | <a href="https://discord.gg/krsBcABm7u"> |
13 | 13 | <img src="https://img.shields.io/discord/308323056592486420?label=discord&logo=discord&logoColor=white&color=7289DA" alt="Join our Discord" /></a> |
14 | 14 | </p> |
15 | 15 |
|
16 | | -# Nabla Asset Manifests |
| 16 | +# Nabla Asset Module |
17 | 17 |
|
18 | 18 | ## Introduction |
19 | 19 |
|
20 | | -This repository provides the NAM consumer module together with the first-party |
21 | | -Nabla manifest registry and release-backed payload channels, without forcing |
22 | | -large binary payloads into normal Git history. |
| 20 | +This repository provides the NAM consumer module together with the smoke, |
| 21 | +documentation, vendored `ExternalData` patch, and CI needed to keep the |
| 22 | +consumer-side build graph stable. |
23 | 23 |
|
24 | | -The repository itself is first-party Nabla infrastructure, but the consumer |
25 | | -module is not meant to be Nabla-only. Other projects can vendor |
| 24 | +The official first-party Nabla manifest registry now lives in: |
| 25 | + |
| 26 | +- `https://github.com/Devsh-Graphics-Programming/Nabla-Asset-Manifests` |
| 27 | + |
| 28 | +The module itself is not meant to be Nabla-only. Other projects can vendor |
26 | 29 | `nam.cmake`, keep their own `.dvc`-based manifest repository, publish payloads |
27 | 30 | through `GitHub Release assets`, and reuse the same build-time materialization |
28 | | -model. |
| 31 | +model without changing consumer call sites. |
29 | 32 |
|
30 | 33 | Current scope is intentionally narrow. For now the only supported remote |
31 | 34 | payload backend is `GitHub Release assets`, and no additional backends are |
@@ -56,9 +59,9 @@ At a high level this follows the same pattern used by mature package and artifac |
56 | 59 | - content-addressed external test data in `CMake ExternalData`, used by projects such as `VTK` |
57 | 60 |
|
58 | 61 | The same consumer module is also meant to stay reusable beyond Nabla itself. |
59 | | -This repository is the first-party Nabla registry, but consumers can point the |
60 | | -module at a different manifest checkout and a different `GitHub Release` |
61 | | -channel without changing the build-graph model. |
| 62 | +The default first-party registry is `Devsh-Graphics-Programming/Nabla-Asset-Manifests`, |
| 63 | +but consumers can point the module at a different manifest checkout and a |
| 64 | +different `GitHub Release` channel without changing the build-graph model. |
62 | 65 |
|
63 | 66 | ## Evidence |
64 | 67 |
|
@@ -139,7 +142,7 @@ This is the exact consumer model we want: |
139 | 142 | - no requirement for consumers to know which remote backend served the blob |
140 | 143 |
|
141 | 144 | <p align="center"> |
142 | | - <img src="https://devsh-graphics-programming.github.io/Nabla-Asset-Manifests/auxiliary/externaldata-flow-kitware.jpg" alt="CMake ExternalData content flow" width="560" /> |
| 145 | + <img src="https://devsh-graphics-programming.github.io/Nabla-Asset-Module/auxiliary/externaldata-flow-kitware.jpg" alt="CMake ExternalData content flow" width="560" /> |
143 | 146 | </p> |
144 | 147 | <p align="center"> |
145 | 148 | <sub>reference: <a href="https://www.kitware.com/cmake-externaldata-using-large-files-with-distributed-version-control/">kitware</a></sub> |
@@ -183,7 +186,7 @@ Release publishing policy in this prototype is intentionally simple: |
183 | 186 | - standalone assets are published as individual files |
184 | 187 | - bundles are published as zip archives |
185 | 188 |
|
186 | | -## Target layout |
| 189 | +## First-party registry layout |
187 | 190 |
|
188 | 191 | <details> |
189 | 192 | <summary>Click to expand</summary> |
@@ -233,4 +236,6 @@ licenses/ |
233 | 236 |
|
234 | 237 | This is only the starting point. |
235 | 238 |
|
236 | | -The repository is intentionally designed so that the rest of the current Nabla `media` tree can be migrated here later under the same model. |
| 239 | +The official first-party Nabla registry is intentionally designed so that the |
| 240 | +rest of the current Nabla `media` tree can be migrated there later under the |
| 241 | +same model. |
0 commit comments