Chris Oliver

You want to save it to the default location by just hitting ENTER. What's the failure say?

Ah perfect. In that case, I think you'd be best off with devise_token_auth. It's designed more for that use case.

Hey Saul,

I've never actually used devise_token_auth but it sounds like it might do the same thing. I'm not entirely sure. It seems to do the same thing as devise_token_authenticatable but provides more functionality. It definitely seems to be helpful if you're using React or Angular.

I guess maybe the best question is what are you trying to accomplish?

Ha! Thanks for catching that typo :)

I'm actually using a suite of Vim plugins called Janus and I'm not sure what plugin it is that does that. It's definitely one of them listed here. Also I'm using MacVim which probably helps to provide that functionality. http://github.com/carlhuda/...

It's now back in the navbar! :)

Yes, very soon! I'm going to add that this morning. Totally forgot I deleted that during the design and that was my bad. :)

That's much better! I'd clean this up too slightly since you're repeating the exclude every time.

  def search
    @images = Image.excluding(@excluded_image_ids)
    if @params[:commit] == "View Uncategorized Images"
      @images.unfinished
    elsif @tags.empty? && @year.empty?
      @images.default
    else
      @images.by_tags(@tags).by_year(@year).none_if_all
    end
  end

Absolutely! Just posted it here: https://github.com/excid3/g...

The difference is just that the PPA gets updated more often (if the maintainer keeps up to date) vs the Ubuntu repo which only gets updated once every major version change. You'll get a stable version of Nodejs, but it will only receive small updates and security fixes, not major version changes.

1. I think the key piece there is modifying the find_for_authentication method. You'll have to join the user and company tables to get only the users for that company. Adjusting that query so that you work through the associated company will do the trick.

2. What's up with background jobs? If you do need background jobs, there's a apartment-sidekiq gem that can help by switching background jobs into the correct tenant.

Actually I just found this: https://github.com/influitive/apartment/pull/208

Looks like you might need to set the environment variables he mentioned in order to get pg_dump to run correctly. Wish I had found this earlier for you!

Read the Rails and Nginx logs to check for errors. I didn't cover the part of setting up the database.yml and secrets.yml files.

There's actually a lot going on here and I can see several bugs because there is logic smattered all over. My impression is that you've extracted lines of code into their own methods too early before you knew exactly what you were trying to accomplish. That left you with a bunch of methods and several of them having their own little bits of logic. There's no clear path that anything flows which makes it hard to understand at a glance.

I think you have felt this and recognized it, so the question is how do I get back to sanity? And the answer is by making your code uglier. Remove all these method calls and put the code back inline. You only call most of these methods from a single place so removing the methods and putting them back inline clarifies things a lot. You can then see what's duplicated. Make the search method contain all the logic and then refactor it.

From what I can tell you always want to exclude the image ids, yet you do this in many different places so it's hard to realize that. Your search method could actually start by calling Image.excluding first and then tack on the other scopes instead. I'd do a refactoring myself and maybe a video of it if I had the time, but hopefully that makes sense as an approach to start refactoring.

It sounds like you may not be passing in the right database username. You should put in the username that you use to login to the database. It will be the same username in your config/database.yml file. For example, mine is -U chris in the command.

Awesome! :) Let me know if there's anything I could cover that would be helpful too.

I believe I covered a bit more of this in a following episode, but you're absolutely right. This is where a form object of some sort makes a lot of sense. You can have it wrapping these things and then translate it to errors in the UI. This being a rake task makes that hard, but a controller variable for a form object would help that.

Haha! Thanks :)

What are the collection_id and selected images parts? I could use a little more context to determine what I'd suggest but I don't think you're far from a good solution.

[Edited]

So all the Time instances in Rails include a date with the Time. It will default to January 1st, 2000 as you can see but you can safely ignore that portion of the output.

You should be able to query the database just by doing this and it should ignore the Date portion of the time. Check the development logs for the SQL query to make sure it does.

 Fpclass.where('start_time>?', Time.zone.now)