cliffmccarthy 0a2ade038c refactor: Reorder deploy_chatmail() ...

- The previous commits that added Deployer classes mostly kept
  deployment operations in the same order that they were in before.
  To organize the process into separate stages for install, configure,
  and activate, we need to reorder the method calls.  This is the
  commit that does that, and thus this is the commit that has the
  largest effect on the order of operations.
- The calls for the deployer objects are all reordered here so that
  the methods are called in the same sequence for each stage.  This
  will allow us to collect the calls into loops in the next commit.
  This commit provides a way to see a diff showing exactly how the
  sequence changed.
- The sequence of deployers was largely based on preserving the order
  of the "activate" stage, as this seems like the place order might be
  the most likely to matter.  Installation of packages and
  configuration of files should generally be able to run in any order.
  (ChatmailDeployer handles updating the apt data, and therefore needs
  to be first, however.)

2025-11-12 19:16:51 -06:00

..

src/cmdeploy

refactor: Reorder deploy_chatmail()

2025-11-12 19:16:51 -06:00

pyproject.toml

CI: ignore PLC0415 in ruff (imports outside top level)

2025-06-29 19:49:17 +02:00