Doc Hawkins posted:

You'll want to install RVM first, before rubygems. See if that helps.

In an odd coincidence, lately I've been contributing to a set of instructions for that kind of thing.

If you have any problems with the Ubuntu section (besides it not giving working urls for the rubygems packages for 8.04 and 8.10), please let me know: we're going to walk a ton of people through this on Friday, and I want to get out in front of any mistakes or unclear bits.

NotShadowStar posted:

Ruby forks aren't real OS forked processes, they're handled by the Ruby VM. If you're needing to do that for supporting multiple cores, fire up multiple Ruby processes communicating through DRB or something or use NodeJS. It just added true multithreading.

hepatizon posted:

Yeah could you elaborate on this and Bonzo's comment? I thought they were real processes (although information on multiprocessing in Ruby seems pretty scant), unlike the fake threads in 1.8.7.

NotShadowStar posted:

It doesn't really matter what RDBMS you're using as long as you stick to AR migrations. You can develop locally on sqlite and push to Heroku and Postgre without too much issue.

A MIRACLE posted:

I've run into issues where my local sqlite queries ran fine, but imploded when I deployed to Heroku on postgres.

For example, a simple case-insensitive search
Works in SQLite:

code:

  def self.search(search)
    if search
      where('name LIKE ? OR description LIKE ?', "%#{search}%", "%#{search}%")
    else
      scoped
    end
  end

the same for Postgres:

code:

  def self.search(search)
    if search
      where('name ILIKE ? OR description ILIKE ?', "%#{search}%", "%#{search}%")
    else
      scoped
    end
  end

I like SQLite for it's portability (I never write very big apps). I'm open to suggestions as to how to make the same code behave on both databases.

Pardot posted:

For most simple crud apps, sure that's fine. But postgres has a ton of great features that you'll want to eventually take advantage of. Fulltext search that doesn't suck, using more than one index per query (sorry mysql), true serializable snapshot isolation, etc etc etc

8ender posted:

Just a quick question about Postgres. In a former (enterprise) life I used to be big into Oracle. I'm now using MySQL with our Rails projects and still a little uncomfortable with the syntax. I've heard that Postgres is similar to Oracle. Is this true? Is it worth checking out?

8ender posted:

Just a quick question about Postgres. In a former (enterprise) life I used to be big into Oracle. I'm now using MySQL with our Rails projects and still a little uncomfortable with the syntax. I've heard that Postgres is similar to Oracle. Is this true? Is it worth checking out?

Pardot posted:

I've never used oracle myself, though.

rugbert posted:

Is anyone still experiencing git push issues with heroku? I keep timing out but the support page says everything is fixed.

A MIRACLE posted:

Not having any problems, pushed last night. Are you on Windows?

Doc Hawkins posted:

You'll want to install RVM first, before rubygems. See if that helps.

In an odd coincidence, lately I've been contributing to a set of instructions for that kind of thing.

If you have any problems with the Ubuntu section (besides it not giving working urls for the rubygems packages for 8.04 and 8.10), please let me know: we're going to walk a ton of people through this on Friday, and I want to get out in front of any mistakes or unclear bits.

Newbsylberry posted:

Sorry for this, but I am copying code from the tutorial guide, and it's giving me all types of errors. I have Rails 3.1.1, and ruby 1.9.2p290.

A MIRACLE posted:

I'm a noob help me.

I want my form select tags to retain their search parameters.

code:

# this works fine
text_field_tag :keyword, params[:keyword], :class => "form_field"

# this doesn't keep the param
select(params[:results_per_page], "results_per_page", ["10", "30", "100"])

# neither does this
select(params[:group_id], "group_id", Group.all.collect { |g| [raw(g.group_name), g.id] }, { :include_blank => true })

manero posted:

BonzoESC posted:

Unless the sites are going to share users, I'd just put each one in a separate Heroku instance and maybe write a rake task that git pushes to each one to deploy. That way you don't have to worry about columns or schemata at all.

enki42 posted:

Yeah, actually I tend to skip by this approach and it's effective as long as you're not sharing data or have a large number of sites (large being anything more than 5 or so in my experience). We actually used this approach at my company until the number of clients became infeasible to manage separately.