deploy_user¶
Synopsis¶
Provisions a dedicated system user for automated deployments, ensures matching UID/GID for cross-node consistency, generates and installs SSH keys, hardens
sshd_configto allow only the deploy user, and drops a.profilethat activates the app’s Python virtualenv on interactive login.The role depends on the
build_dependenciesrole (seemeta/main.yml). Setup tasks are taggedsetup,neverand are skipped unless the playbook is invoked with--tags=all,setup.
Parameters¶
Parameter |
Comments |
|---|---|
Application identifier used as a comment in the generated |
|
Path to the currently-active deploy directory. Referenced by the |
|
Optional mapping of extra environment variables to export from the deploy user’s |
|
Name of the deployment user and its primary group. Default: |
|
Login shell for the deployment user. Default: |
|
Numeric UID for the deployment user; also used as the GID for the matching primary group so file ownership is consistent across nodes (important for |
|
Filesystem root under which the app is installed. When defined, the generated |
|
Optional path fragment prepended to Default: |
|
Deployment environment name (e.g. |
|
Existing webserver group on the target system. The deployment user is added as a supplementary member so it can write to shared web-server-owned files (logs, media, etc.). Default: |