gabrieljoelc/eat_the_food

Yet another attempt to make Docker + Rails + Heroku work. Futures: migrate to Kubernetes

eat_the_food's Issues

See if it deploys to GCP

I'd like to just smoke test the current setup in GCP Container Engine.

Migrate Q&A to Bootstrap carousel

Right now the Q&A are vanilla Rails views. Let's make 'em carousely.

https://getbootstrap.com/docs/4.0/components/carousel/#with-indicators

Run email de-dup in background job and push notification with ActionCable

Depends on #3

Add frontend UI tests

Docker ignore test directories

It'd be nice if we could also include a .dockerignore.web that corresponds with the Dockerfile.web. Apparently, there isn't a way to choose the ignore file yet: moby/moby#12886.

Add Tina to homepage

See the README.md

Unit tests for email distincting

Ensure sub-processes and resources work in production

From #2:

• Other sub-processes/resrouces to still be tested:
  • ActiveMail - SMTP
  • ActiveJob - Redis
  • ActionCable - Redis, CORS
  • Cache - Redis

Some things we might need:

• Dockerfile.sidekiq
• Dockerfile.cable
  so we can do (see this doc):

heroku container:push --recursive
=== Building web
=== Building sidekiq
=== Building cable

Also, consider renaming website to web in docker-compose.yml to align with the web Dyno process.

Make email de-duping work

• Make autoloading (for development) work for /lib
• Figure out how to load a monkey patch (I cheated and require_relative in application.rb
• Make eager loading (for production) work for /lib
• UI for 100 emails and single test (no user input for # of emails or tests)
• require: false for faker

# config/development.rb
+= %W[#{config.root.join('lib')}] # can't get working
+= Dir["#{config.root}/lib/**/"] # didn't work either

# config/application.rb
# got this working after I moved it to this file ¯\_(ツ)_/¯
+= [config.root.join('lib'), config.root.join('lib', 'distincitifier')]

Sandbox implementation

Resources

http://blog.bigbinary.com/2016/08/29/rails-5-disables-autoloading-after-booting-the-app-in-production.html
https://stackoverflow.com/a/7204837/34315

Make app work with one Dockerfile for all environments

It'd be nice if I knew the same image that was running locally for development would be the one running in staging/production.

Improve environment variables for CI/CD

• Ability to deploy new ones
• Ability to require them
• Common interface despite different backends (i.e. Heroku vs. Codeship vs. locally)

Distinct email distincter index improvements

• Allow user to input:
  • Email count
  • Number of tests to run
• Display benchmark data

UI improvements

• Remove "Test nav item"
• Add Tina image to homepage
• Link to see for yourselves and email de-dup
• Add Tina image to header
• Make homepage weird