Re: Heroku and Sequel Migrations

2010-08-25 Thread Robert Eanes
Never used this tool, but I would suggest you look at the source of the 
'sequel' script and see what it's doing. If it's running those migrations with 
some ruby code, then that code is what you need to have in your db:migrate task.

Also, you may have better luck describing the heroku environment to people in 
the sequel project's community and asking how they would get it to work, since 
there doesn't seem to be anybody else on this group using it.


On Aug 25, 2010, at 9:23 AM, Scott LaBounty wrote:

 Josh,
 
 Yes, that's the sequel I'm referring to. Sorry I didn't make it clearer.
 
 What I'm looking for is the what would go into the rake db:migrate task. When 
 I run locally, I do something like:
 
 sequel -m dbMigration -M 1 sqlite://db.sqlite
 
 which does the database migrations in the directory dbMigration to version 
 1 and creates the sqlite database db.sqlite in the current directory. 
 
 When I try to just do a system 'sequel --version' in the heroku console, I 
 just get false returned which I assume means that sequel is not available.
 
 I can do a heroku db:push sqlite://db.sqlite and make everything work fine, 
 but I'd like to be able to do migrations (and use the postgresql database 
 provided) and that's what I'm currently stuck on.
 
 Thanks again,
 
 Scott
 
 On Wed, Aug 25, 2010 at 7:12 AM, Josh Coffman joshcoff...@gmail.com wrote:
 ..hoping someone smarter than me will jump in here...
 
 At first I though you meant sql; so I searched and found this:
 http://sequel.rubyforge.org/
 
 Is that what you are using? I'm just using sqlite, and have used mysql. It 
 should work about the same for any supported db. Here's what I do for 
 migrations in a rake task:
  `heroku db:migrate --app timesheettoaster`
 
 That calls the command line to migrate on heroku and specifies the app to use 
 because I have 2; one for live, one for test.
 
 What happens when you try? error? 
 
 
 
 On Wed, Aug 25, 2010 at 6:14 AM, Scott LaBounty slabou...@gmail.com wrote:
 Josh,
 
 Thanks for the idea, but it still doesn't work. I stripped it down a bit 
 further and tried to just run it from a Heroku console (figuring to add it to 
 rake later) with 
 
 # heroku console
  system sequel --version # Hoping here to get something back showing that 
  sequel is available
 = false # Looking like sequel, the command, is not available at least not in 
 this way
 
 Am I totally missing something here or is this just not doable with Sequel 
 and Heroku?
 
 Thanks again,
 
 Scott
 
 
 On Tue, Aug 24, 2010 at 4:04 PM, Josh Coffman joshcoff...@gmail.com wrote:
 call the heroku cli from your rake task.
 http://docs.heroku.com/heroku-command
 
 
 
 
 On Mon, Aug 23, 2010 at 6:33 AM, Scott LaBounty slabou...@gmail.com wrote:
 All,
 
 I'm trying to figure out how to have run a sequel migration on Heroku. Here's 
 the rake task that I can use locally ...
 
 
 namespace :db do
task :migrate do
version = ENV['VERSION'] ? -M #{ENV['VERSION']} : 
system sequel -m dbMigration #{version} #{ENV['DATABASE_URL']
 || 'sqlite://library.sqlite'} 
end
 end
 
 
 Does anyone have any good way to use Sequel migrations on Heroku? Hints? 
 Anything?
 
 -- 
 Scott
 http://steamcode.blogspot.com/
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/heroku?hl=en.
 
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/heroku?hl=en.
 
 
 
 -- 
 Scott
 http://steamcode.blogspot.com/
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/heroku?hl=en.
 
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/heroku?hl=en.
 
 
 
 -- 
 Scott
 http://steamcode.blogspot.com/
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 

Re: Rails3 RC from master failed to start

2010-08-06 Thread Robert Eanes
Specifying gems with :path seems to work, so rather than pushing gems to a 
public place like rubygems.org you can pull them into your own app git repo 
temporarily and point to them with a relative path.
for example:
gem 'acts-as-taggable-on', :path = vendor/gemtmp/acts-as-taggable-on

This is working for me, anyway.

On Aug 5, 2010, at 5:06 PM, Chris Conley wrote:

 Yeah I agree. I should've mentioned that it was a temporary solution. Thanks!
 
 On Thu, Aug 5, 2010 at 5:59 PM, Nick Quaranto n...@quaran.to wrote:
 How about git://github.com/rails/rails.git ?
 Also, I've been trying to discourage gem forking unless if it's really,
 really necessary...you can point bundler to a git repo, why is pushing the
 gem necessary then?
 
 On Thu, Aug 5, 2010 at 5:56 PM, Chris Conley chris.m.con...@gmail.com
 wrote:
 
 I just got around this by forking the git gem and pushing to
 rubygems.org. Here's drnic's guide to doing just that:
 
 http://drnicwilliams.com/2009/11/04/hacking-someones-gem-with-github-and-gemcutter/
 
 On Thu, Aug 5, 2010 at 5:33 PM, Chris Conley chris.m.con...@gmail.com
 wrote:
 Yeah, I'm getting the same error as well.
 
 On Thu, Aug 5, 2010 at 5:11 PM, lstoll l...@lds.li wrote:
 I'm having a similar problem - seems that any gem that is installed
 from a git source will fail like this.
 
 On Aug 5, 10:47 pm, morgoth w.wnetr...@gmail.com wrote:
 After pushing application to heroku I get
 error:http://gist.github.com/510350
 
 Anybody having similar problem?
 
 --
 You received this message because you are subscribed to the Google
 Groups Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/heroku?hl=en.
 
 
 
 
 --
 You received this message because you are subscribed to the Google Groups
 Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/heroku?hl=en.
 
 
 --
 You received this message because you are subscribed to the Google Groups
 Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at
 http://groups.google.com/group/heroku?hl=en.
 
 
 -- 
 You received this message because you are subscribed to the Google Groups 
 Heroku group.
 To post to this group, send email to her...@googlegroups.com.
 To unsubscribe from this group, send email to 
 heroku+unsubscr...@googlegroups.com.
 For more options, visit this group at 
 http://groups.google.com/group/heroku?hl=en.
 

-- 
You received this message because you are subscribed to the Google Groups 
Heroku group.
To post to this group, send email to her...@googlegroups.com.
To unsubscribe from this group, send email to 
heroku+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/heroku?hl=en.