This repo has been created to document my progress on the Dissecting Ruby on Rails 5 course.

Despite the course being based on rails 5, I built this application in Rails 6 with a modernized approach. I took the course as a refresher on the framework to accommodate my new job role. Regardless of its age the course still covers a mountain of useful information regarding best practices and the Rails ecosystem.

Deployment of the app was done via Heroku, using the Redistogo addon.

Visit the app here

• Login/Sign Up with varying admin/user permissions
• CRUD Blogs
• CRUD Portfolios
• Drag and drop portfolio cards
• AWS Image Uploader
• Live Twitter Feed
• Live Action Cable Commenting
• Categorization of blogs and portfolios
• Gravatar profile images

The following environment variables will need to be added to a .env file in the projects root directory, the project requires an AWS S3 bucket and Twitter API keys. For more information on how to generate your own keys visit:

Twitter API Docs

AWS S3 Docs

Your .env will need to be formatted as follows:

S3_BUCKET_NAME=your-bucket-name
AWS_ACCESS_KEY_ID=XXXXXXXXXXXXXXXXXXXX
AWS_SECRET_ACCESS_KEY=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
AWS_REGION=your-region-#

TWITTER_CONSUMER_KEY=XXXXXXXXXXXXXXXXXXXXXXXXX
TWITTER_CONSUMER_SECRET=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
TWITTER_ACCESS_TOKEN=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX
TWITTER_ACCESS_TOKEN_SECRET=XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

Your cable.yml file will need the production URL changed to the following if your running the project locally.

<%= ENV.fetch("REDIS_URL") { "redis://localhost:6379/1" } %> 

Before running the project ensure you run

rails db:setup

Followed by

bundle install 

Run any pending migrations with

rails db:migrate 

Optionally run

rails db:seed 

Install Yarn dependencies

yarn install

Finally run

rails s

Testing for models has been added using RSpec, these can be found in the spec directory.

To run tests use

bundle exec rspec

For Capybara feature tests to run ensure your system has Google Chrome installed, alternatively update Capybara's default driver to use one of your choosing. This can be done in the feature test specs found in the spec/features directory.