Chris Oliver

Almost forgot to post an update. Looks like everything deployed just fine with no problemos! 😎

Because we set the bucket name in the secrets.yml, you can just change that for each environment just like you would do with any other secrets.

# config/initializers/shrine.rb
  bucket:            Rails.application.secrets.aws_bucket,

# config/secrets.yml
development:
  aws_bucket: app-development

staging:
  aws_bucket: app-staging

production:
  aws_bucket: app-production

Make sense?

Yeah you should be safe. I'm actually upgrading GoRails to 5.0.1 as we speak so I will report back if I have any issues.

I saw the announcement blog post last night on http://rubyonrails.org.

Github's build stuff is probably for master, not necessarily for the release unless you're looking at the tag for 5.0.1.

I'm not sure what all was included in it, but I know that Phusion talked about the slow client DoS they fixed in Puma for this release: https://blog.phusion.nl/2016/12/21/actioncable-under-stress-protecting-your-application-against-slow-clients-using-passenger/

The auth stuff is going to be fun. So many different methods.

Brilliant! :D

Thanks Matias! :)

That makes sense. I noticed Chrome doing this with videos recently so I figured it might be the same. Photoshop is pretty smart about detecting what you intended to shoot as and everything but Chrome can only do the basic orientation stuff that's set.

You should also be able to add a processor into Shrine to have imagemagick correct the orientation on upload as well. There's an "auto_orient" method you can use with MiniMagick to do that automatically.

I'm not sure if this matters (I know it does with video) but do your photos happen to have been taken at the other orientation originally? I'm not sure if the browser may be reading some metadata and rotating them automatically or not.

I'm using this Chrome plugin: https://github.com/callumlo...

I sure hope they get these issues with thor sorted out soon

Rails shouldn't cache project names or anything. Spring might, there have been a few times recently where I noticed I had to run spring stop to fix a couple odd bugs that seemed like things were cached when they shouldn't be.

Sounds like the apartment-sidekiq gem isn't finding the tenant.

11:34:10 worker.1  | 2016-12-19T15:34:10.798Z 7489 TID-ox4vqdyhs WARN: Apartment::TenantNotFound: One of the following schema(s) is invalid: "companydemo" "public"

I just came across this in thor recently. I didn't have the same errors you have, but it is that latest thor release. It actually originally broke all new rails apps for a couple hours, then they released a patch, but still has issues it looks like.

https://github.com/erikhuda/thor/issues/533

These things you're seeing is probably something similar.

You could probably try setting thor in your Gemfile to "0.19.11" which was the version that wasn't causing any trouble previously.

gem "thor", "= 0.19.11"

Yeah, it's pretty incredible to see how far it's come. All thanks to you guys in the community though. Couldn't do it without you. 💕

Awesome to have the debugging option, and it makes sense that you don't want misspellings in that situation. Search is complex. Haha

Pretty crazy, it's been 2 years already!

Searchkick's docs for autocomplete show using this which should tell it to index those with the word_start option, so I believe that's all I did.

class Book < ActiveRecord::Base
  searchkick word_start: [:title, :author]
end

https://github.com/ankane/searchkick/#instant-search--autocomplete

You doing something different?

Yep, you can upload any file type you want with Paperclip, Carrierwave, or Shrine. I like Shrine the most personally, it's nice and modular so that's what I'd personally recommend using.

Thanks Alex! I had a lot of fun recording these episodes each day. I think they turned out great, but I think it was the naming or something that got them underwatched.

Update: I actually tried out the zip file from S3 approach on this and it worked really really well. I just compiled on Ubuntu and zipped up the ~/.rbenv/versions/2.3.3 directory and uploaded it to S3. Install scripts just download and extract that to the same location, and then run rbenv rehash so rbenv can setup all the proper shims to know that version is available. Worked like a charm!