Pwas CLI — Full-stack Pwas deploys, one command

overview

Not just a deploy script.
A Pwas project manager.

Pwas CLI manages isolated projects/<name>/ — Framework, Orchestrator, Client and Pwas.MicroService.DocsResolver, each with its own Docker network, volumes and ports — plus a handful of operations on the shared codebases themselves: tests, code generation, production-ready builds.

commands

Every lifecycle stage, one command.

Every command has its own pwas <comando> --help with more detail.

pwas create

Creates projects/<name>/ with its own docker-compose.yml, .env and per-project configuration, seeded from Pwas.Framework/Config and Pwas.Client/config — ports assigned automatically based on creation order.

pwas run / stop / logs

With or without service names, they operate on the entire project or only on framework-api, orchestrator, client, microservice-docsresolver and the other services in its docker-compose.yml.

pwas build

Updates KEY VALUE in whichever of the three project .env files already contains that key — no need to remember which of the three a given setting lives in.

frequently asked

Pwas CLI: the questions.

Do we need the CLI to put a project into production?

No: the CLI produces standard images you can publish to your registry and release with the procedures you already use. It's a productivity tool for creating, starting and managing projects, not a compulsory step in your release chain.

What does it mean that projects are isolated?

Every project has its own network, volumes, ports and generated secrets, assigned automatically based on existing projects. The practical consequence is that you can have several projects on the same machine with no conflicts and nothing configured by hand.

Does it modify existing installations?

Regeneration works on the project copy, not on shared code: project operations stay confined to the project. That's a deliberate property, because the worst failure mode in tools like this is the one that touches something it shouldn't have.

Does it work on Windows or only Linux?

It works wherever container execution works, which today means all the main development platforms. Some local convenience features, such as host name management, behave in operating-system-specific ways.

Can it be used in a continuous integration chain?

Yes: the test and image build commands are designed for non-interactive use too, and produce standard artefacts. Integration with your existing chain doesn't require tooling from us.

What happens if we delete a project?

Removal concerns the project environment: network, containers and volumes. Because the domain declaration consists of files versioned wherever you choose, recreating an environment means recreating containers and restoring data, both in ordinary formats.

Full-stack deploy.
One command.

Not just a deploy script.
A Pwas project manager.

Every lifecycle stage, one command.

Pwas CLI: the questions.

Ready to
run the stack.

Full-stack deploy.One command.

Not just a deploy script.A Pwas project manager.

Every lifecycle stage, one command.

Pwas CLI: the questions.

Read next.

Ready torun the stack.

Full-stack deploy.
One command.

Not just a deploy script.
A Pwas project manager.

Ready to
run the stack.