confighooks

[Nizari]

Hello!

First of thank you for this repo. Some nice extra info!
I was wondering if you also have confighooks? Based on https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-linux-extend.html#platforms-linux-extend.example when you for example update your environment variables, a different set of hooks seems to be triggered. Or am I seeing this wrong?

[Nizari]

P.S. I have now a full workflow as well. It differs in a couple of aspects from whats inside here, but if you're interested let me know. I'm glad to help.

[rennokki]

Well, as far as I see, this concept is new to me and I didn't know it exists. From what I read, whenever the environment receives a configuration update (switching from Nginx to Apache or vice-versa, changing autoscaling, settings, etc.), it runs some arbitrary code. I can't find a specific use-case for Laravel to run something when the AWS Configuration changes.

I personally don't think Laravel needs to run something when the configuration changes. Prolly is a good idea to refresh nginx or something on configuration update, but I'll look at it.

I'll tag this as enhancement and perhaps it will be some scaffolding in the future.

[Nizari]

Well, as far as I see, this concept is new to me and I didn't know it exists. From what I read, whenever the environment receives a configuration update (switching from Nginx to Apache or vice-versa, changing autoscaling, settings, etc.), it runs some arbitrary code. I can't find a specific use-case for Laravel to run something when the AWS Configuration changes.

I personally don't think Laravel needs to run something when the configuration changes. Prolly is a good idea to refresh nginx or something on configuration update, but I'll look at it.

I'll tag this as enhancement and perhaps it will be some scaffolding in the future.

The only case I can think of is when you change environment variables. While testing I'm 99% sure it only runs the webhooks from the confighooks directory and not from the normaal hooks folder. You can verify this in the eb-engine.log. If that isn't the case for you then it's not really required

[rmsj]

@Nizari how did you solve this?

[rmsj]

Noobie question, How would you start the environment?
Via EB console, or command line? How?

[Nizari]

@rmsj sorry for the late reply. Github notifications are making it hard to see spam from real.
Below a example of the folder structure.

You can read all details here https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/platforms-linux-extend.html

[Nizari]

Noobie question, How would you start the environment?
Via EB console, or command line? How?

I use the AWS EB CLI. With that you can easily create new environments. It has many cool other funcitons like downloading a entire config file of your EB environment which you can use to quickly create new environments (in case you current EB environment is corrupt for some reason)

https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/eb-cli3-configuration.html