-
Notifications
You must be signed in to change notification settings - Fork 99
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
Job won't open the correct .env-file in Job? #84
Comments
Hi, but from which domain you dispatch the job? I ask you because to my knowledge there is no way to run a command/job under a certain domain/environment if you launch it from within the Laravel script ran under another domain/environment. Cheers Giacomo |
Sorry for the delayed reply. Then you pushed the job under the domain: |
yes... to my knowledge there is no way to "change the environment" from within the application itself. There is the need of some "machinery" outside the application which dispatch the jobs among the domains. I think that in some way this is similar to another issue #14 which also could be solved only using a proper shell script. I hope this helps... I close the issue for now... be free to reopen if you need Cheers Giacomo |
Dear Community,
i'am dispatching a Job like this and in my job i want to Send an API-Request.
For the Request i need the Keys from the correct ENV file. But unfortunately the Job open the
.env
and not the.env.domain
My Scheduler works with
php artisan schedule:run --domain=domain
I hope that you understand my Question and know a solution.
The text was updated successfully, but these errors were encountered: