title: Running rake db:seed on AWS Elastic Beanstalk
body: <p>I'm trying to deploy my first rails app using Elastic Beanstalk, and I've gotten to the point where I need to seed my database with approximately half a million records. My initial attempt was to create a .config file in my .ebextensions folder and then use git aws.push from the command line, but it kept giving me timeout errors.</p>
  
  <p>So, I abandoned that and decided to just directly ssh into my EC2 instance and run it from there. However, that's not working for me either. I cd into var/app/current, and then ran rake db:seed RAILS_ENV=production. It seems to run for a minute or two, then outputs 'killed' before exiting.</p>
  
  <p>I also attempted to seed just one record, just to see if the size of the file had anything to do with it. If I do that, it springs an error telling me that my SQLITE database is read only. I'm pretty sure my db is set up to use MySQL in production, I changed database.yml to use the various ENV variables, and when I run eb status from the command line, it tells me that MySQL is being used.</p>
  
  <p>The weird thing is, I swear I did these exact same steps earlier yesterday, sshing in and seeding the database, and it worked. The only problem was I made a few changes, terminated the app and decided to start over, and now it doesn't work at all. Any ideas what I'm doing wrong? This is a Rails 4.1/Ruby 2.1 setup.</p>