PHPAML

Documentation · Chapter 18

Model the remote host explicitly.

A deployment profile records host, user, destination, transport, and strategy. Secrets and private keys stay outside version control.

Every lesson starts from the problem, explains the mechanism, then gives a concrete verification.

LESSON OBJECTIVE

What you will be able to do

Choose and validate the deployment strategy appropriate to the host before writing remotely.

Choose the strategy for the host

releases fits SSH hosts with symlinks, public-html fits shared hosting, and sftp-only supports hosts without shell access.

phpaml — zsh
aml deploy:configure staging --host example.com --user deploy --path /srv/app
aml deploy:check staging
aml deploy staging --dry-run

Check before changing

deploy:check validates connectivity, destination, permissions, runtime needs, and available strategy without releasing.

Preview with dry-run

dry-run compares manifests and reports additions, changes, and deletions without writing remotely. Review unexpected removal.

CHECKPOINT

Before you continue

Did deploy:check and dry-run explain destination, permissions, planned changes, and unexpected deletions before deployment?