This repository has been archived by the owner on May 4, 2021. It is now read-only.
Backup script does not have the right environment when running with CRON_TIME #23
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
March 23, 2016 23:25
… backup instead of the last one.
…ckup would totally fail because cron run them from empty environment.
|
What's the status on this being merged? |
|
I was wondering why this cron setting didn't work :) |
|
+1 would be great to get this merged. As at present cron isn't working for me ;( |
|
Is there a reason why this isn't merged? Would be awesome if it did! |
|
Can this PR be merged? |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cron runs every task with a fresh environment, hence everything fails because the AWS keys and others necessary env variables are not defined.