I am currently working on a project that I wanted to run on AWS ElasticBeanstalk Setup but now I heared of Laravel Vapor. I signed up and tried it. I do have some questions and maybe some of you do know the answer to it already or could provide me with some ideas:
My "deployment hooks" are always failing, I'm only running the example script "php artisan migrate --force" and nothing else. Database is of course created and credentials are set correctly (verified that in the environment itself)
I want to run a multi domain page, example1.com and example2.com are pointing to the same instance and should both run my Laravel app. Any ideas, how to achieve that with Vapor? (I'm aware of the wildcard part. Would it be possible to point the domains to the load-balancer I can start within Vapor?
Multiple domains isn't supported at the moment but it's something we're planning for the future.
As for your first question, I'll need to take a look at your setup and your vapor.yaml file so I can stand on why the migrate command isn't working, most of the time it's because Lambda is unable to communicate with your DB instance.
Hey, thanks for your reply. Just sent you the email.
I thought, that for now I still could be possible to have the load balancer in place and "manage" the mutli domain mapping on my own right? So when creating the load balancer, I should be able to point many domains (in my case example1.com and example2.com) to this LB and it will redirect it into my Laravel instance.
Or am I wrong here?