Denis Mysenko
Denis Mysenko
Hmm, isn't this a bit dangerous? It will add extra routes automatically - without explicit consent from the user? I understand auto discovery may be good for some packages that...
@Omranic more details please? what option exactly?
@jwpage the rationale is that this could potentially be a security (informational) risk - automagically adding routes that allow anybody to execute code on your instances. it feels reasonable that...
@arjunksankar are you using config() helper in the code that in turn uses env() function?
@mstnorris hmm, how does it affect the worker exactly? I thought it's just an AWS setting and the worker wouldn't even realize it's popping from a FIFO queue?
@faculezcano could you please give a real-world example of when a config would be cached? I always assumed that you set the environment variable once and pretty much don't have...
@jlorente this is correct for basic installations (with .env files). in case of AWS - we are talking brand new containers every time and real environment variables only. Containers are...
@jlorente if you are deploying unique files (stateful) in your containers, why not just include a config file with values then? for variables that are longer than 4096 characters. if...
@mubbashar every command will only be executed once - by one of the worker instances, the one that pops the job from the queue first (even though technically with AWS...
@reganjohnson one scheduled command (eg. hourly()) will only be passed and processed by one worker - whichever worker pulls from the queue first