@cyaxis/ulvia 1.0.7 → 1.0.8

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/INSTALLATION.md CHANGED
@@ -249,24 +249,24 @@ For a local installation:
249
249
 
250
250
  ```bash
251
251
  ulvia services start
252
- ulvia instance create registry --profile ulvia.repository@1.0.0
252
+ ulvia instance create registry --profile repository@1.0.0
253
253
  ulvia instance status registry
254
254
  ulvia instance credentials registry
255
255
  ```
256
256
 
257
257
  The Registry API is available below
258
- `http://registry.localhost:5100/.cms/call/ulvia.repository`. Its public identity
258
+ `http://registry.localhost:5100/.cms/call/ulvia/repository`. Its public identity
259
259
  endpoint is `GET /v1/info` relative to that prefix. Ordinary CMS instances do not
260
260
  expose this contract. The profile creates ordinary CMS Pages for the public
261
261
  catalogue, search, resource details, registration/login and personal namespaces,
262
- publications and PAT management. These Pages use the `ulvia-repository` collection
263
- and shared `ulvia-official` resources.
262
+ publications and PAT management. These Pages use the `ulvia/repository` collection
263
+ and shared `ulvia/mossa` resources.
264
264
 
265
265
  For public hosting, configure network exposure and ACME as described in section 6
266
266
  before creating instances, then create the application on its public domain:
267
267
 
268
268
  ```bash
269
- ulvia instance create registry --domain repository.example.com --profile ulvia.repository@1.0.0
269
+ ulvia instance create registry --domain repository.example.com --profile repository@1.0.0
270
270
  ```
271
271
 
272
272
  Replace the example domain with a domain routed to this host. The same shared
@@ -275,7 +275,7 @@ proxy handles its HTTPS certificate. Provider management remains on loopback.
275
275
  ### Publisher Accounts And Credentials
276
276
 
277
277
  Registration, password login and PAT management use the normal Access bindings
278
- under `/.cms/call/ulvia.cms.access`. Registration follows the instance policy.
278
+ under `/.cms/call/ulvia/cms.access`. Registration follows the instance policy.
279
279
  An ordinary account can claim and publish; it does not need CMS administrator
280
280
  privileges. The protected publisher operations use a shared CMS PAT.
281
281
 
@@ -308,7 +308,7 @@ Publication never installs a collection on a site.
308
308
  Namespace claims are atomic and limited to 32 owned names per account. Transfer
309
309
  uses an explicit target account and expected revision. Suspension retains the
310
310
  name; account deletion is refused while it owns namespaces. Startup does not
311
- reserve or reclaim names, including `ulvia.official`.
311
+ reserve or reclaim names, including `ulvia`.
312
312
 
313
313
  ### Restart And Updates
314
314
 
@@ -329,7 +329,7 @@ credentials remain in the normal CMS storage.
329
329
  A profile change is separate from an image replacement:
330
330
  `ulvia instance upgrade-profile registry ID@VERSION`. The target must be a
331
331
  supported explicit transition shipped by the Provider and retain the
332
- `ulvia.repository` application ID. The CLI saves the exact new reference only
332
+ `ulvia/repository` application ID. The CLI saves the exact new reference only
333
333
  after the Provider acknowledges it. Restart never selects a different profile.
334
334
 
335
335
  Back up the Provider database, file storage, matching encryption credentials and
package/README.md CHANGED
@@ -41,13 +41,13 @@ bun run ulvia -- services stop
41
41
  bun run ulvia -- upgrade edge --version 0.0.1-beta
42
42
  bun run ulvia -- upgrade provider --version 0.0.1-beta
43
43
  bun run ulvia -- reset --yes
44
- bun run ulvia -- release packages/official-repository/collections/ulvia-official
44
+ bun run ulvia -- release packages/official-repository/collections/mossa
45
45
  bun run ulvia -- release /path/to/contract-directory
46
46
  bun run ulvia -- release /path/to/provider-directory
47
- bun run ulvia -- push contract ulvia.official/ulvia.cms.installations@1.0.0 --repository https://repository.example
48
- bun run ulvia -- pull collection ulvia.official/ulvia-official@1.0.0 --repository https://repository.example
49
- bun run ulvia -- yank collection ulvia.official/ulvia-official@1.0.0 --repository https://repository.example --reason "Superseded"
50
- bun run ulvia -- restore collection ulvia.official/ulvia-official@1.0.0 --repository https://repository.example
47
+ bun run ulvia -- push contract ulvia/cms.installations@1.0.0 --repository https://repository.example
48
+ bun run ulvia -- pull collection ulvia/mossa@1.0.0 --repository https://repository.example
49
+ bun run ulvia -- yank collection ulvia/mossa@1.0.0 --repository https://repository.example --reason "Superseded"
50
+ bun run ulvia -- restore collection ulvia/mossa@1.0.0 --repository https://repository.example
51
51
  bun run ulvia -- prune
52
52
  ```
53
53
 
@@ -115,7 +115,7 @@ profile:
115
115
 
116
116
  ```bash
117
117
  ulvia services start
118
- ulvia instance create registry --profile ulvia.repository@1.0.0
118
+ ulvia instance create registry --profile repository@1.0.0
119
119
  ulvia instance status registry
120
120
  ```
121
121
 
@@ -187,8 +187,8 @@ Contract fixture assets declared in `definition.json` are read from
187
187
  `fixtures/<asset-id>` and verified by digest. Releasing the same coordinate with
188
188
  different content fails. Local release storage is a private CLI cache, not an
189
189
  HTTP server. `push` publishes it to the configured CMS Repository; its public
190
- catalogue and downloads use admitted `ulvia.repository` bindings under
191
- `/.cms/call/ulvia.repository`. CMS installation and Provider administration
190
+ catalogue and downloads use admitted `ulvia/repository` bindings under
191
+ `/.cms/call/ulvia/repository`. CMS installation and Provider administration
192
192
  consume those public sources. `prune` empties the local cache without deleting
193
193
  service or instance data.
194
194
 
@@ -217,7 +217,7 @@ availability and every immutable artifact. For single pushes, transfer required
217
217
  dependencies first.
218
218
 
219
219
  ```bash
220
- ulvia push ulvia.official/ulvia.cms.emailer@1.0.0
220
+ ulvia push ulvia/cms.emailer@1.0.0
221
221
  ulvia push all
222
222
  ```
223
223
 
@@ -304,7 +304,7 @@ exact manifest claims. Provider behavior is covered by implementation-owned test
304
304
  The current baseline uses fresh `1.0.0` official releases and `v1` local state.
305
305
  Each named instance uses `<name>.localhost` unless an explicit domain is supplied;
306
306
  `default` is an ordinary name. Repository hosting uses a CMS instance with the
307
- `ulvia.repository@1.0.0` profile. Client PAT connections and local release caches
307
+ `repository@1.0.0` profile. Client PAT connections and local release caches
308
308
  are separate from the shared services and instance lifecycle.
309
309
 
310
310
  ## Collection examples