rstack dev: run a project's products together for development, without Studio
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 30/100
Piste de recherche
Start by reading the existing bregctl dev start and bregctl dev stop flows, the product activation steps, and related issue #2214 on port allocation. The proposal defines a cross product runner, isolated PostgreSQL resources, a test issuer, plan validation, TTL cleanup, and Registry Studio integration; it leaves key design questions open. Done means the acceptance scenarios pass on Linux and macOS, including concurrent runs and cleanup.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Why
A project that uses several products, for example a BReg registry and a Casework service for a licensing journey, has no single command that runs them together for development. Each product has its own <product>ctl dev mode with its own database container and issuer, and nothing starts them as one run with shared test people. Registry Studio tests a saved project through its own runner, but an adopter working from a plain Git checkout, an agent or a CI job without Studio cannot do the same.
Proposal
rstack dev runs the products of one project directory as one isolated development run.
rstack dev start <project-dir> [--database-url <url>] [--ttl <duration>] [--json]
rstack dev status <run-id> [--json]
rstack dev token <run-id> --as <test-person> [--json]
rstack dev stop <run-id>
The verbs follow bregctl dev start and bregctl dev stop.
Inputs
- The project's product files, exactly as they are deployed.
rstack devchanges nothing in them and needs no development-only settings inside them. - One small dev plan file in the project, with a schema published with each release. It names the test people per role and the client each one acts through, the order the products start in, and the journey to check once the run is ready. Registry Studio writes it when it publishes a project; an adopter writes it by hand.
- A PostgreSQL server address. Each run creates its own databases and roles there, so a run needs no Docker.
What a run does
- Starts a test issuer private to the run. It signs under the project's issuer name with a key made for that run, and the products trust it for that run only, so a token from one run is refused by another run and by a deployed system.
- Activates each product as a deployment does (for BReg: check, package, apply, verify), then serves it on loopback on free ports.
- Runs the plan's journey check and reports the result.
Output, as text or as JSON with --json: the run ID, each product's URL, the journey result, and how to get a token per test person (rstack dev token). The run holds until stop or until its TTL passes. stop removes the run's databases, roles, keys and scratch files.
Acceptance
- From a plain Git checkout of a licensing example project (a BReg registry and a Casework service) with no Studio installed,
rstack dev startbrings both products up and the plan's journey passes, on Linux and macOS. - Two runs of the same project at the same time never share a database, role, port, key or token.
rstack dev stopand an expired TTL leave nothing behind on the PostgreSQL server or on disk.- A malformed dev plan is refused before anything starts, naming the field.
- Registry Studio's test runs use this command, so there is one implementation of a development run.
Scope
- First: BReg and Casework. Other runtime products join as their run contracts allow.
- Later, separate: a browser sign-in page on the test issuer, so a UI host can sign a test person in.
- Not in scope: TLS between products, production deployment, and hosted previews (a hosting service can build on this command).
Open questions
- When no
--database-urlis given, shouldrstack dev startstart a local PostgreSQL from a pinned image, as the product dev modes do? That is friendlier on a laptop; requiring an address keeps the command free of Docker. - Should the per-product
devmodes stay as they are for single-product work, or later delegate torstack dev? - The dev plan's file name and where it sits in a project.
Related: #2214 (one port block per product for dev starts).
- Langage dominant
- Rust
- Étoiles
- 2
- Forks
- 0
- Merge moyen
- 9 h 48 min
- PR mergées (30 j)
- 151
Préparer son environnement
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de registrystack/registry-stack
-
area:breg enhancement
Difficulté 2/5 1-3 heures Accessibilité débutants 65/100
registrystack/registry-stack#2765 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 62/100
registrystack/registry-stack#2761 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 70/100
registrystack/registry-stack#2743 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
registrystack/registry-stack#2706 ·
Les mainteneurs répondent en général sous 1 jour
-
macOS contributor gates: Messaging config tests fail under the symlinked macOS temporary directoryOuverte
Difficulté 2/5 1-3 heures Accessibilité débutants 83/100
registrystack/registry-stack#2704 ·
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de registrystack/registry-stack
Issues similaires
-
help wanted needs investigation priority: low
Difficulté 2/5 1-3 heures Accessibilité débutants 62/100
-
[Bug] 建议把黑白主题设置同步到启动页面Ouvertebug
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
AstrBotDevs/AstrBot-desktop#197 ·
-
bug
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
tomast1337/Puppeter-PptxGenJS#440 ·
-
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
n0-computer/iroh#4709 ·
Les mainteneurs répondent en général sous 1 jour
-
生词本里,已标记为认识的词,按钮写「不认识了」读着别扭Ouverte
Difficulté 1/5 Moins d'une heure Accessibilité débutants 75/100
qingjian-team/qingjian#1114 ·
Les mainteneurs répondent en général sous 2 jours