Yaswanth Mangalagiri

  Django   deployment never fails unless it is at the Database drivers. The required version of mysqlclient isn't found. is the common error you get in  Amazon Web Services  server logs If you are here after reading my pervious post then you must have wasted days while deploying your  Django  app on ElasticBean The only reason of failure could be the installion of the mysql drivers. The regular DB driver that django installs or in your requirement.txt file is mysqlclient You try the below mysql Drivers:  mysql-python mysql-connector-python For my app  mysql-connector-python worked. Go through this site https://dev.mysql.com/downloads/connector/python/

There is always an issue with  Amazon Web Services  ElasticBean while deploying applications and always a scary part. It was a cakewalk on Heroku hosting platform but it's nightmare here and wastes days  The Rails Application   use Puma as default server, recently it has updated to 5.2.2 at the time of writing this post. During the recent deployments to AWS elasticbean all have been failing, The main reason is the Gem File isn't being obeyed.  The specified version of the Puma isn't being instaled by the AWS serves when  A revolution for server I decided to go back to Django again. You can read this post to encounter what all I encountered duint the deployments of Django Application. So going back to Rails. Everything has been installed properly except the Puma server.  I specified 4.3.2 in my Gem File but AWS was installing the 5.2.2. And all the Load Balancers have been showing the status of 502 or 400. The Server health is shown as degraded or severe. Here are the steps