Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch to owner change instead of shh user change #3763

Merged
merged 1 commit into from
Jan 11, 2024

Conversation

MartijnCuppens
Copy link
Contributor

Fixes #3542

@antonmedv antonmedv merged commit 1c4f208 into deployphp:master Jan 11, 2024
8 of 9 checks passed
@MartijnCuppens MartijnCuppens deleted the patch-1 branch January 11, 2024 10:52
midweste pushed a commit to midweste/deployer that referenced this pull request Jan 16, 2024
* upstream/master: (78 commits)
  [automatic] Update docs with bin/docgen
  Move Caddy file in to separate file (deployphp#3765)
  Create parent folders if needed (deployphp#3764)
  [automatic] Update docs with bin/docgen
  Switch to owner change instead of shh user change (deployphp#3763)
  Don't show warning if `become` parameter is set to `root` (deployphp#3761)
  [automatic] Update docs with bin/docgen
  Adding Spiral Framework recipe (deployphp#3582)
  Crontab: allow sudo with crontab:use_sudo option (deployphp#3759)
  fix: run cachetool without args (deployphp#3742)
  Fix version variables in Contao recipe (deployphp#3735)
  contrib: fix creating cron jobs first time
  Removing wrong information regarding reverse DNS (deployphp#3726)
  [automatic] Update docs with bin/docgen
  Fix issue provoked after adding array casting and returning empty fcgi parameter to the command (deployphp#3724)
  Revert "[TASK] Update TYPO3 recipe (deployphp#3674)" (deployphp#3723)
  ci-cd docs: update link to gitlab doc section (deployphp#3721)
  [automatic] Update docs with bin/docgen
  Fix test function (deployphp#3717)
  [automatic] Update docs with bin/docgen
  ...
@alanzheng88
Copy link

alanzheng88 commented Sep 23, 2024

hi @MartijnCuppens, this assumes that we're able to log in as deployer user via ssh to deploy. if we need to log in as a different user to deploy, how should we go about doing this? im wondering if it would make sense to make the <user>:<group> configurable

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Please login as the user \"ubuntu\" rather than the user \"root\ during provisioning
3 participants