No description
  • HTML 77.7%
  • Python 22.3%
Find a file
Repository files (latest commit first)
Filename Latest commit message Latest commit date
drorganvidez dae0bc079c License under LGPL-3.0-or-later
The feature had no license, so legally nobody could use, change or share
it, which is what the marketplace exists for. It now carries the license of
the SPLENT catalog, LGPL-3.0-or-later. A product that uses it can carry any
license of its own, and changes to the feature itself stay open.
COPYING.LESSER and COPYING hold the texts and pyproject.toml declares them,
so the next release takes them to PyPI.
2026-10-11 11:49:45 +02:00
src feat: ✨ uvlhub API keys pages, scopes and X-API-Key header 2026-10-08 10:08:56 +02:00
.gitignore feat: ✨ uvlhub API keys pages, scopes and X-API-Key header 2026-10-08 10:08:56 +02:00
COPYING License under LGPL-3.0-or-later 2026-10-11 11:49:45 +02:00
COPYING.LESSER License under LGPL-3.0-or-later 2026-10-11 11:49:45 +02:00
MANIFEST.in feat: ✨ uvlhub API keys pages, scopes and X-API-Key header 2026-10-08 10:08:56 +02:00
pyproject.toml License under LGPL-3.0-or-later 2026-10-11 11:49:45 +02:00
README.md feat: ✨ uvlhub API keys pages, scopes and X-API-Key header 2026-10-08 10:08:56 +02:00

splent_feature_apikeys_uvlhub

The apikeys_uvlhub feature of a SPLENT product line.

A SPLENT feature is a Python package that a product composes with others: its models, routes, services, templates and hooks are registered when the product starts. What this feature provides and requires is listed in the [tool.splent.contract] section of pyproject.toml, which splent feature:contract --write keeps in sync with the source.

Use it in a product

splent feature:add splent_feature_apikeys_uvlhub

Develop

splent feature:test splent_feature_apikeys_uvlhub
splent feature:contract splent_feature_apikeys_uvlhub

Release

splent feature:release splent_feature_apikeys_uvlhub --dry-run --bump patch
splent feature:release splent_feature_apikeys_uvlhub

The first command rehearses the release and changes nothing. The second publishes it to the git forge and to PyPI, and a PyPI version is permanent.