About
Registry of software product lines and listed feature repositories, and the relay that publishes UVL models to UVLHub
Provides
FeatureListingSplSplKeyCallSplRelease
FeatureListingServiceSplRegistryService
/api/v1/features/api/v1/spls/api/v1/spls/<name>/api/v1/spls/<name>/releases/api/v1/spls/<name>/releases/<int:version>/marketplace/spls/<name>
es
Commands
-
$
splent feature:spl_registry feature-visibility REPOSITORY VALUEPut a listed feature back in the index, or take it out.
-
$
splent feature:spl_registry featuresEvery feature repository developers listed, withdrawn ones too.
-
$
splent feature:spl_registry listEvery product line in the registry, with its pointer.
-
$
splent feature:spl_registry reconcile [SPL_NAME]Look on UVLHub for the DOI of every release whose outcome is unknown.
-
$
splent feature:spl_registry set-owner SPL_NAME EMAILHand a product line to a developer, so they can publish releases of it.
-
$
splent feature:spl_registry settle SPL_NAME VERSION [OPTIONS]Record what an administrator found out about an undetermined release.
-
$
splent feature:spl_registry stuck [OPTIONS]Releases whose outcome nobody knows.
-
$
splent feature:spl_registry visibility SPL_NAME VALUEShow a product line in the public index, or withdraw it from it.
Run them in your workspace once the feature is installed in the selected product.
Configuration
| Setting | Default | What it does |
|---|---|---|
UVLHUB_URL |
https://www.uvlhub.io
|
No description yet. |
UVLHUB_API_KEY |
empty | The instance's publishing credential, so the default is empty. The real value belongs in the deployment's .env, which is not committed. |
SPL_REGISTRY_PUBLISHING_ENABLED |
false
|
Publishing is off until a deployment turns it on, so an instance brought up to look around cannot push to a public registry by accident. |
SPL_REGISTRY_VERIFY_PUBLISHED |
true
|
Whether a release is read back after publishing to confirm it landed. |
SPL_REGISTRY_GATE_TIMEOUT_SECONDS |
10
|
Timeouts, in seconds: the gate check is meant to be quick, the upload is not, because a model with its files takes a while. |
SPL_REGISTRY_UVLHUB_TIMEOUT |
60
|
No description yet. |
SPL_REGISTRY_UVLHUB_PUBLISH_TIMEOUT |
600
|
How long the calls that mint a DOI may wait on Zenodo. They run in the background, so the developer is never kept waiting on them. |
SPL_REGISTRY_QUOTA_WINDOW_HOURS |
24
|
Quotas. The window they are counted over, then the ceilings: per user, per SPL, and across the instance, so one account cannot spend a shared registry's budget. |
SPL_REGISTRY_MAX_RELEASES_PER_USER |
10
|
No description yet. |
SPL_REGISTRY_MAX_RELEASES_PER_SPL |
5
|
No description yet. |
SPL_REGISTRY_MAX_RELEASES_TOTAL |
100
|
No description yet. |
SPL_REGISTRY_MAX_SPLS_PER_USER |
0
|
No description yet. |
SPL_REGISTRY_MAX_FEATURES_PER_USER |
50
|
No description yet. |
These are the defaults. A product changes them in its own pyproject.toml, under [tool.splent.config], or in .env.deploy in production.
Dependencies
In product lines
-
marketplace_spl
Optional in this line
Needs
apikeysauth
Extension points
spl_registry/detail.htmlspl_registry/not_found.html
FeatureListingServiceSplRegistryService
FeatureListingSplSplKeyCallSplRelease
Other features fill its hook slots. A refinement can override its templates and services or extend its models without forking it.
Compatibility
>=3.13
>=1.30.0
requests>=2.31