0xk175un3 said over 4 years ago on Deploying to AWS Elastic Beanstalk :
Could you plz update this video? Bc for now there is some issues with Rails 5.2 bc of using another secret variables technique, and also there is no more allowed to run command like `db:create` inside ssh connection.

David Kimura PRO said over 4 years ago on Deploying to AWS Elastic Beanstalk :
When you ssh into the EC2 instance, try doing this to get the database created. ``` sudo su bundle exec rails db:create exit ``` I believe they've changed the permissions of the ec2 user and you cannot login as the www user.

0xk175un3 said over 4 years ago on Deploying to AWS Elastic Beanstalk :
Yeap, this work, thx a lot!

Flo Bee Jones said over 3 years ago on Deploying to AWS Elastic Beanstalk :
It worked. I can't say this with science, but I believe the difference was using rails new maple --skip-active-storage, so not using storage blob. Otherwise, I couldn't make it work when connected to a postgres database inside of an RDS. Also, when making my RDS instance, I added the database name 'ebdb' in the 'Additional Configuration' section. (I believe that's what section was called.)

HundredBillion said almost 3 years ago on Deploying to AWS Elastic Beanstalk :
How did you get the SECRECT_KEY_BASE file in your rails app?

David Kimura PRO said almost 3 years ago on Deploying to AWS Elastic Beanstalk :
  In this example, the SECRECT_KEY_BASE is an environment variable and is used in the config/secrets.yml.  Within AWS Beanstalk's Configuration Overview (Elastic Beanstalk > Environments > Your App > Configuration), you can create an Environment Property which is where you set the environment variables. Any environment variable set here will be available to the EC2 instances that are created.

Login to Comment