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

Nesting crontab config doesn't work #3769

Open
SimJoSt opened this issue Jan 16, 2024 · 0 comments
Open

Nesting crontab config doesn't work #3769

SimJoSt opened this issue Jan 16, 2024 · 0 comments

Comments

@SimJoSt
Copy link
Contributor

SimJoSt commented Jan 16, 2024

  • Deployer version: 7.3.3
  • Deployment OS: Ubuntu 22.04
import:
  - contrib/crontab.php

config:
  crontab:
    identifier: 'application'
    jobs:
      - '* * * * * cd {{current_path}} && {{bin/php}} wp-cron.php >> /dev/null 2>&1'

As nesting is supported by the hosts node, supporting multiple remote hosts, I tried the same in the config node with the crontab config. Unfortunately, this configuration threw the following "error" (it just didn't recognize the config was set):

➜  dep crontab:sync
task crontab:sync
[linode.coders.fail] Nothing to sync - configure crontab:jobs

We had to switch to the following configuration, listing each option for crontab directly instead of nesting it:

config:
  ssh_copy_id: false
  crontab:identifier: 'hellseatic'
  crontab:jobs:
      - '* * * * * cd {{current_path}} && {{bin/php}} wp-cron.php >> /dev/null 2>&1'

Since the rewrite it seems to be mandatory, to provide an identifier, so the sections in the crontab work.
It would also be great if it would work without one, using a fallback. That's another story, though.

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

No branches or pull requests

1 participant