To fix this issue you have to run following commands
Go to current folder like below path and you will find current deployed app there.
Step to fix this issue: SSH to one of your instances. Go to /var/log/ run “tail -50 eb-activity.log” this will give an idea why it fails so you will be able to fix it.
I made a list where if you want to force redirect from Elastic Beanstalk you can follow these steps 👇
Liskov Substitution SubClass should be replaceable with base class without any behavior breaks. To fix above code, we can do something like this Coding to interface will be how to follow liskuv principle, always make sure that all functions in classes implements same interface will return same type; else you will find yourself violating liskuve […]
Open-Closed Principle (OCP) Open for extension closed for modification. To fix above code, we can do something like this Now when we have change-request in requirements to add paypal method, all we have to do is adding another paypal class implements same PaymentInterface and thats it, so we extended(open for extension) our application with paypal […]
Single Responsibility Principle (SRP) A class or function should have one and only one reason to change To fix above code, we can do something like this Now you have 2 classes each one has one responsibility, with Laravel you can apply “Single Action Controller” method to make sure each class has only one responsibility.
Here the error generated when i tried to make composer update Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 72 bytes) in phar:///usr/local/bin/composer/src/Composer/DependencyResolver/Solver.php on line 700 To fix this you can run composer update without memory limit php -d memory_limit=-1 /usr/local/bin/composer update
If you are new to Vim i can recommend this blog by Derek Wyatt it’s good even if you want some strength in Vim.