rpotter6298
5c095b19a5
The checkout is now astrape/astrape-dashboard, not astrape/astrape-dashboard/<package>. The package contents move to the repository root and pyproject maps the package name to '.' via package-dir, with the subpackages listed explicitly. The systemd units move out to /srv/astrape/deploy/systemd, outside every repository, because they describe this deployment rather than any one component. Verified both install modes: editable, which is how the deployment runs, and a plain wheel install, which is what the container build does. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
18 lines
788 B
TOML
18 lines
788 B
TOML
[build-system]
|
|
requires = ["setuptools>=68"]
|
|
build-backend = "setuptools.build_meta"
|
|
|
|
[project]
|
|
name = "astrape-dashboard"
|
|
version = "0.1.0"
|
|
description = "Astrape web frontend"
|
|
requires-python = ">=3.12"
|
|
dependencies = ["gibil", "astrape-ems", "astrape-oracle"]
|
|
|
|
# Flat layout: this repository *is* the package. package-dir maps astrape_dashboard to the
|
|
# repository root rather than to a nested astrape_dashboard/ directory, so the checkout is
|
|
# astrape/astrape-dashboard and not astrape/astrape-dashboard/astrape_dashboard.
|
|
[tool.setuptools]
|
|
packages = ["astrape_dashboard", "astrape_dashboard.classes", "astrape_dashboard.classes.displays", "astrape_dashboard.scripts", "astrape_dashboard.scripts.daemons", "astrape_dashboard.scripts.debug"]
|
|
package-dir = {"astrape_dashboard" = "."}
|