Skip to content

Job naming prefix in case of shared hosting#55112

Closed
maierwalter wants to merge 4 commits intolaravel:12.xfrom
maierwalter:patch-1
Closed

Job naming prefix in case of shared hosting#55112
maierwalter wants to merge 4 commits intolaravel:12.xfrom
maierwalter:patch-1

Conversation

@maierwalter
Copy link

Possibility for prefixing name of jobs, so that if you have a shared hosting and 2 jobs with the same name that should run "onOneServer", it would still run for both environments. In case you don't have the property set in the env, the functionality will be the same without affecting current changes.

In order to solve this now, I have to add the prefix for each command in Kernel.

possibility for prefixing name of jobs, so that if you have a shared hosting and 2 jobs with the same name that should run "onOneServer", it would still run for both environments
@Neol3108
Copy link
Contributor

You should use config instead of env because env is not available when config is cached

@maierwalter
Copy link
Author

I've made a mistake and did not notice, I am sorry, working on fixing it

@taylorotwell
Copy link
Member

Thanks for your pull request to Laravel!

Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.

If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!

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

Successfully merging this pull request may close these issues.

3 participants