Do not source venv from inside script #340
Open
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
|
My first try sourcing the conf file in CRON line failed : source </path/to/config> && /path/to/cron_bano.sh That's why I rolled it back to the current behavior. Can you suggest the correct command line to put in the crontab ? |
|
Je pense qu'il faut passer par un commande bash: Mais je vois qu'il y a d'autres façon de faire |
frodrigo
force-pushed
the
no_source_venv
branch
2 times, most recently
from
c17650a
to
7b17ecd
Compare
|
Rebase on |
frodrigo
force-pushed
the
no_source_venv
branch
from
7b17ecd
to
d0cd14c
Compare
frodrigo
force-pushed
the
no_source_venv
branch
from
d0cd14c
to
c39301e
Compare
|
Je reactive ce PR. Et rebsé. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Warning: breaking change.
The source command should be added to the crontab file.