service-foundation 0.0.1__tar.gz

service_foundation-0.0.1/PKG-INFO

@@ -0,0 +1,45 @@
+Metadata-Version: 2.4
+Name: service-foundation
+Version: 0.0.1
+Summary: Foundation for standalone runnable services: composition and launcher, browser and workload authentication surfaces, token issuance, configuration, health and readiness, migration invocation.
+Author: Elena Viter
+License: MIT
+Project-URL: Homepage, https://github.com/elenaviter/app-ecosystem
+Project-URL: Repository, https://github.com/elenaviter/app-ecosystem
+Classifier: Development Status :: 1 - Planning
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# service-foundation
+
+Foundation for standalone runnable services.
+
+An application that also ships as its own service needs a second ground
+beyond [`app-foundation`](../app-foundation/README.md): something has to
+compose the adapters and launch, authenticate a browser session (OIDC)
+and a service workload, issue and verify the service's own opaque tokens,
+read configuration, answer health and readiness, and invoke the
+migrations the application owns. This package is that ground, once, so a
+standalone host of an application (the planned standalone Connection Hub
+among them) is a thin launcher rather than a project.
+
+Scope boundary, deliberately strict:
+
+- service composition and launcher contracts;
+- browser-session (OIDC) and service-workload authentication surfaces;
+- opaque-token issuance and verification for the service's own sessions;
+- configuration surface, health and readiness;
+- migration invocation (the migrations themselves belong to the app).
+
+service-foundation contains no authority models (those are
+[`prokura`](../prokura/README.md)), no application behavior, and no
+KDCube bundle concepts. It stands on `app-foundation` and is what a
+`services/<name>` launcher stands on.
+
+**Version 0.0.1 claims the name.** The modules arrive with the standalone
+host work; the running implementation lives inside
+[KDCube](https://github.com/kdcube/kdcube) today.
+
+Home: https://github.com/elenaviter/app-ecosystem

service_foundation-0.0.1/README.md

@@ -0,0 +1,31 @@
+# service-foundation
+
+Foundation for standalone runnable services.
+
+An application that also ships as its own service needs a second ground
+beyond [`app-foundation`](../app-foundation/README.md): something has to
+compose the adapters and launch, authenticate a browser session (OIDC)
+and a service workload, issue and verify the service's own opaque tokens,
+read configuration, answer health and readiness, and invoke the
+migrations the application owns. This package is that ground, once, so a
+standalone host of an application (the planned standalone Connection Hub
+among them) is a thin launcher rather than a project.
+
+Scope boundary, deliberately strict:
+
+- service composition and launcher contracts;
+- browser-session (OIDC) and service-workload authentication surfaces;
+- opaque-token issuance and verification for the service's own sessions;
+- configuration surface, health and readiness;
+- migration invocation (the migrations themselves belong to the app).
+
+service-foundation contains no authority models (those are
+[`prokura`](../prokura/README.md)), no application behavior, and no
+KDCube bundle concepts. It stands on `app-foundation` and is what a
+`services/<name>` launcher stands on.
+
+**Version 0.0.1 claims the name.** The modules arrive with the standalone
+host work; the running implementation lives inside
+[KDCube](https://github.com/kdcube/kdcube) today.
+
+Home: https://github.com/elenaviter/app-ecosystem

service_foundation-0.0.1/pyproject.toml

@@ -0,0 +1,27 @@
+[build-system]
+requires = ["setuptools>=68", "wheel"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "service-foundation"
+version = "0.0.1"
+description = "Foundation for standalone runnable services: composition and launcher, browser and workload authentication surfaces, token issuance, configuration, health and readiness, migration invocation."
+readme = "README.md"
+license = { text = "MIT" }
+authors = [{ name = "Elena Viter" }]
+requires-python = ">=3.10"
+classifiers = [
+    "Development Status :: 1 - Planning",
+    "License :: OSI Approved :: MIT License",
+    "Programming Language :: Python :: 3",
+]
+
+[project.urls]
+Homepage = "https://github.com/elenaviter/app-ecosystem"
+Repository = "https://github.com/elenaviter/app-ecosystem"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+service_foundation = ["py.typed"]

service_foundation-0.0.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

service_foundation-0.0.1/src/service_foundation/__init__.py

@@ -0,0 +1,14 @@
+"""service-foundation: foundation for standalone runnable services.
+
+Service composition and launcher contracts, browser-session (OIDC) and
+service-workload authentication surfaces, opaque-token issuance for the
+service's own sessions, configuration, health and readiness, and
+migration invocation. No authority models (those are `prokura`), no
+application behavior, no KDCube bundle concepts; it stands on
+`app-foundation`.
+
+Version 0.0.1 claims the name; the modules arrive with the standalone
+host work. Status: https://github.com/elenaviter/app-ecosystem
+"""
+
+__version__ = "0.0.1"

service_foundation-0.0.1/src/service_foundation.egg-info/PKG-INFO

@@ -0,0 +1,45 @@
+Metadata-Version: 2.4
+Name: service-foundation
+Version: 0.0.1
+Summary: Foundation for standalone runnable services: composition and launcher, browser and workload authentication surfaces, token issuance, configuration, health and readiness, migration invocation.
+Author: Elena Viter
+License: MIT
+Project-URL: Homepage, https://github.com/elenaviter/app-ecosystem
+Project-URL: Repository, https://github.com/elenaviter/app-ecosystem
+Classifier: Development Status :: 1 - Planning
+Classifier: License :: OSI Approved :: MIT License
+Classifier: Programming Language :: Python :: 3
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+
+# service-foundation
+
+Foundation for standalone runnable services.
+
+An application that also ships as its own service needs a second ground
+beyond [`app-foundation`](../app-foundation/README.md): something has to
+compose the adapters and launch, authenticate a browser session (OIDC)
+and a service workload, issue and verify the service's own opaque tokens,
+read configuration, answer health and readiness, and invoke the
+migrations the application owns. This package is that ground, once, so a
+standalone host of an application (the planned standalone Connection Hub
+among them) is a thin launcher rather than a project.
+
+Scope boundary, deliberately strict:
+
+- service composition and launcher contracts;
+- browser-session (OIDC) and service-workload authentication surfaces;
+- opaque-token issuance and verification for the service's own sessions;
+- configuration surface, health and readiness;
+- migration invocation (the migrations themselves belong to the app).
+
+service-foundation contains no authority models (those are
+[`prokura`](../prokura/README.md)), no application behavior, and no
+KDCube bundle concepts. It stands on `app-foundation` and is what a
+`services/<name>` launcher stands on.
+
+**Version 0.0.1 claims the name.** The modules arrive with the standalone
+host work; the running implementation lives inside
+[KDCube](https://github.com/kdcube/kdcube) today.
+
+Home: https://github.com/elenaviter/app-ecosystem

service_foundation-0.0.1/src/service_foundation.egg-info/SOURCES.txt

@@ -0,0 +1,8 @@
+README.md
+pyproject.toml
+src/service_foundation/__init__.py
+src/service_foundation/py.typed
+src/service_foundation.egg-info/PKG-INFO
+src/service_foundation.egg-info/SOURCES.txt
+src/service_foundation.egg-info/dependency_links.txt
+src/service_foundation.egg-info/top_level.txt

service_foundation-0.0.1/src/service_foundation.egg-info/dependency_links.txt

@@ -0,0 +1 @@
+

service_foundation-0.0.1/src/service_foundation.egg-info/top_level.txt

@@ -0,0 +1 @@
+service_foundation