Welcome to [Renovate](https://github.com/renovatebot/renovate)! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.
🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.
---
### Detected Package Files
* `Dockerfile` (dockerfile)
* `.github/workflows/build.yml` (github-actions)
* `.woodpecker/build.yml` (woodpecker)
* `.woodpecker/lint.yml` (woodpecker)
### Configuration Summary
Based on the default config's presets, Renovate will:
- Start dependency updates only once this onboarding PR is merged
- Enable Renovate Dependency Dashboard creation.
- Use semantic commit type `fix` for dependencies and `chore` for all others if semantic commits are in use.
- Ignore `node_modules`, `bower_components`, `vendor` and various test/tests directories.
- Group known monorepo packages together.
- Use curated list of recommended non-monorepo package groupings.
- Apply crowd-sourced package replacement rules.
- Apply crowd-sourced workarounds for known problems with packages.
🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to `renovate.json` in this branch. Renovate will update the Pull Request description the next time it runs.
---
### What to Expect
With your current configuration, Renovate will create 9 Pull Requests:
<details>
<summary>chore(deps): pin dependencies</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/pin-dependencies`
- Merge into: `master`
- Upgrade alpine to `sha256:51b67269f354137895d43f3b3d810bfacd3945438e94dc5ac55fdac340352f48`
- Upgrade koalaman/shellcheck-alpine to `sha256:f73b035c8ebfc8a66ba54e07af5cc41e790cf41fff45317914b1ce677dd9cada`
- Upgrade [pipelinecomponents/hadolint](https://gitlab.com/pipeline-components/hadolint) to `sha256:430e949e6554d56ffc2dd08898ee609c71822d7fa1033f7c4dc240e90f2aac23`
- Upgrade plugins/docker to `sha256:2f157400c2cb7de1b309b0f044f119375108218e54d38e1340e00b9f93abdefb`
- Upgrade [zricethezav/gitleaks](https://github.com/gitleaks/gitleaks) to `sha256:e5f6d1a62786affd1abd882ecc73e9353ce78adea1650711f6e351767723712d`
</details>
<details>
<summary>chore(deps): update zricethezav/gitleaks docker tag to v8.18.1</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/zricethezav-gitleaks-8.x`
- Merge into: `master`
- Upgrade [zricethezav/gitleaks](https://github.com/gitleaks/gitleaks) to `sha256:6945c62ca019ead32bc337ab0c9fd055e98d82961765d38b7ccccc84dae95d0f`
</details>
<details>
<summary>chore(deps): update pipelinecomponents/hadolint docker tag to v0.26.0</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/pipelinecomponents-hadolint-0.x`
- Merge into: `master`
- Upgrade [pipelinecomponents/hadolint](https://gitlab.com/pipeline-components/hadolint) to `sha256:7122937006c7a9bcbb78ce764d3c2f0092f183b843ad128bc9fd6ea918e22d5b`
</details>
<details>
<summary>chore(deps): update actions/checkout action to v4</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/actions-checkout-4.x`
- Merge into: `master`
- Upgrade [actions/checkout](https://github.com/actions/checkout) to `v4`
</details>
<details>
<summary>chore(deps): update docker/build-push-action action to v5</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/docker-build-push-action-5.x`
- Merge into: `master`
- Upgrade [docker/build-push-action](https://github.com/docker/build-push-action) to `v5`
</details>
<details>
<summary>chore(deps): update docker/login-action action to v3</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/docker-login-action-3.x`
- Merge into: `master`
- Upgrade [docker/login-action](https://github.com/docker/login-action) to `v3`
</details>
<details>
<summary>chore(deps): update docker/setup-buildx-action action to v3</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/docker-setup-buildx-action-3.x`
- Merge into: `master`
- Upgrade [docker/setup-buildx-action](https://github.com/docker/setup-buildx-action) to `v3`
</details>
<details>
<summary>chore(deps): update docker/setup-qemu-action action to v3</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/docker-setup-qemu-action-3.x`
- Merge into: `master`
- Upgrade [docker/setup-qemu-action](https://github.com/docker/setup-qemu-action) to `v3`
</details>
<details>
<summary>chore(deps): update peter-evans/dockerhub-description action to v4</summary>
- Schedule: ["at any time"]
- Branch name: `renovate/peter-evans-dockerhub-description-4.x`
- Merge into: `master`
- Upgrade [peter-evans/dockerhub-description](https://github.com/peter-evans/dockerhub-description) to `v4`
</details>
<br />
🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for `prhourlylimit` for details.
---
❓ Got questions? Check out Renovate's [Docs](https://docs.renovatebot.com/), particularly the Getting Started section.
If you need any further assistance then you can also [request help here](https://github.com/renovatebot/renovate/discussions).
---
This PR has been generated by [Renovate Bot](https://github.com/renovatebot/renovate).
<!--renovate-config-hash:e80b4e42a3043bc12fa0640db4bac392d2bf770acf841360d7c8ceeeac2ec1a9-->
Reviewed-on: #1
Co-authored-by: Renovate Bot <renovate@mgrote.net>
Co-committed-by: Renovate Bot <renovate@mgrote.net>
The following issues were addressed. Note that these are edge cases.
* If an empty `/cron-scripts` directory was mounted in the container, an
error would occur.
* If files in the `/cron-scripts` directory had spaces in the name, this
would cause issues.
* stdin was held open when running `docker exec` which would cause hangs
and other issues. The `exec` command is now run non-interactively.
* Custom scripts that failed would interrupt processing of scripts after
it, if any.
When the user mounts /cron-scripts in the container, this replaced the built-in
scripts. The built-in scripts are now shipped in /cron-scripts-builtin now.
Transition from Docker Hub automated builds to Github Actions for CI
builds. This allows support for other architectures.
ARM64 support has been added as well. This fixes#5.
It is now possible to override and explicitly specify the shell you
would like used when executing cron tasks. This is accomplished with the
NEXTCLOUD_EXEC_SHELL environment variable, which defaults to bash. You
can also override and customize the arguments provided to that shell
executable via NEXTCLOUD_EXEC_SHELL_ARGS, which defaults to "-c".
See documentation for more detail and examples.
Fixes#6
* New DEBUG environment variable enables `set -x` in shell scripts for
extra verbose output for debugging custom cron scripts and to assist
with development of the core scripts.
* Verify if we can find the Nextcloud container on start up. Fail if
not.
* Print information about how we will search for Nextcloud on start up.
* During cron task execution, the ID of the Nextcloud container is
printed, if found.
If the Nextcloud container is recreated while the cronjob container is still running, the ID of the
container is obtained each time the cron tasks are executed. Previously it was cached on entrypoint,
so if the ID changed this container would fail.
New NEXTCLOUD_EXEC_USER environment variable added which allows control over which
user is used to execute cron tasks inside the Nextcloud container. By default, the
user is `www-data`. If the environment variable is specified but empty, no `--user`
option is provided to `docker exec`.
Mount individual shell scripts (with the `*.sh` extension) inside `/cron-scripts/` in the
container. The cron daemon will automatically run these scripts inside the Nextcloud
container for you. Write the scripts as if they will run in the Nextcloud container
itself.
