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

Log commands and use Environment Variables when using running commands manually #137

Closed
AndreiArdelean1 opened this issue Sep 19, 2020 · 5 comments

Comments

@AndreiArdelean1
Copy link
Contributor

AndreiArdelean1 commented Sep 19, 2020

When running a command manually from the UI it is not logged to file, only to crontab-ui stdout. Also, the Environment Variables are not passed to the command.

@AndreiArdelean1 AndreiArdelean1 changed the title Log commands when using "Run now" button Log commands and use Environment Variables when using running commands manually Sep 19, 2020
@tuxuday5
Copy link

tuxuday5 commented Oct 2, 2020

You mean 'Run Now'? This doesn't seem to use cron. That's why its not logging to any files.
If you want in logs, have to do it explicitly.

@AndreiArdelean1
Copy link
Contributor Author

Yes, 'run now' doesn't use crontab, but even so, it should use the environment variables and should log the output otherwise the crontab and the 'run now' would have different behaviors.

@tuxuday5
Copy link

tuxuday5 commented Oct 2, 2020

Agree with environment vars. For o/p you can do the re-direction by yourself and check. Will look into env vars and check whether it can be fixed quickly!
But please do clarify what you mean by environment vars.

@tuxuday5
Copy link

tuxuday5 commented Oct 2, 2020

Ignore. See that you had modified per your requirement and raised a PR.

@alseambusher
Copy link
Owner

I have merged this #138

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

3 participants