Not sure I'm doin it right #1

Closed
drew1two opened this Issue Feb 21, 2012 · 12 comments

Projects

None yet

2 participants

@drew1two

Getting errors at the 'migrate' stage saying "Don't know how to build task 'migrate'". Could be me though. Would you be able to elaborate a bit more on your installation instructions please.

Cheers

@BrucePerens
Owner

It's "rake db:migrate". You can use "rake -T" to see what all of the
tasks are. I'll fix the document.

 Thanks

 Bruce

On 02/21/2012 09:50 AM, drew1two wrote:

Getting errors at the 'migrate' stage saying "Don't know how to build task 'migrate'". Could be me though. Would you be able to elaborate a bit more on your installation instructions please.

Cheers


Reply to this email directly or view it on GitHub:
#1

@drew1two

Haha, sorry I confused you. the quoted part "Don't know how to build
task 'migrate'" is the Error I get when I run 'rake db:migrate.
My bad :)

I am Very keen to look into this engine of yours as it uses the combination
of gems I've been looking for. Your engine was hopefully going to give me
the platform I wanted.

So would you be able to expand on your install notes and / or look into the
error when I run the migrate? Everything goes according to your
instructions up until that point.

Regards

On Wed, Feb 22, 2012 at 7:21 AM, Bruce Perens <
reply@reply.github.com

wrote:

It's "rake db:migrate". You can use "rake -T" to see what all of the
tasks are. I'll fix the document.

Thanks

Bruce

On 02/21/2012 09:50 AM, drew1two wrote:

Getting errors at the 'migrate' stage saying "Don't know how to build
task 'migrate'". Could be me though. Would you be able to elaborate a bit
more on your installation instructions please.

Cheers


Reply to this email directly or view it on GitHub:
#1


Reply to this email directly or view it on GitHub:

#1 (comment)

@BrucePerens
Owner

On 02/21/2012 10:35 PM, drew1two wrote:

Haha, sorry I confused you. the quoted part "Don't know how to build
task 'migrate'" is the Error I get when I run 'rake db:migrate.
My bad :)
It sounds like you don't have a Rakefile. When Rails creates a skeleton
application, it makes one. To test, make a new Rails app:

rails new test1
cd test1

Edit the Gemfile to add a Javascript engine. I use

 gem 'therubyracer'

Then, see if you can run rake:

 rake db:migrate

This should silently complete.
Then go back to your application and find what's missing.

 Thanks

 Bruce
@drew1two

I made the skeleton first yes. Then followed your instructions.

this is the content of the rakefile as you've prolly seen always

#!/usr/bin/env rake
# Add your own tasks in files placed in lib/tasks ending in .rake,
# for example lib/tasks/capistrano.rake, and they will automatically be
available to Rake.

*
*
require File.expand_path('../config/application', FILE)
*
*
Devise::Application.load_tasks

On Wed, Feb 22, 2012 at 5:42 PM, Bruce Perens <
reply@reply.github.com

wrote:

On 02/21/2012 10:35 PM, drew1two wrote:

Haha, sorry I confused you. the quoted part "Don't know how to build
task 'migrate'" is the Error I get when I run 'rake db:migrate.
My bad :)
It sounds like you don't have a Rakefile. When Rails creates a skeleton
application, it makes one. To test, make a new Rails app:

rails new test1
cd test1

Edit the Gemfile to add a Javascript engine. I use

gem 'therubyracer'

Then, see if you can run rake:

rake db:migrate

This should silently complete.
Then go back to your application and find what's missing.

Thanks

Bruce

Reply to this email directly or view it on GitHub:

#1 (comment)

@drew1two

I am on win7 64bit. Maybe.... dunno.
I really have to look into every gem that looks kewl before I bundle
install them as so many use fork that damn windows dunno anything about.

On Wed, Feb 22, 2012 at 6:02 PM, Drew Parker drewisdad@gmail.com wrote:

I made the skeleton first yes. Then followed your instructions.

this is the content of the rakefile as you've prolly seen always

#!/usr/bin/env rake
# Add your own tasks in files placed in lib/tasks ending in .rake,
# for example lib/tasks/capistrano.rake, and they will automatically be
available to Rake.

*
*
require File.expand_path('../config/application', FILE)
*
*
Devise::Application.load_tasks

On Wed, Feb 22, 2012 at 5:42 PM, Bruce Perens <
reply@reply.github.com

wrote:

On 02/21/2012 10:35 PM, drew1two wrote:

Haha, sorry I confused you. the quoted part "Don't know how to build
task 'migrate'" is the Error I get when I run 'rake db:migrate.
My bad :)
It sounds like you don't have a Rakefile. When Rails creates a skeleton
application, it makes one. To test, make a new Rails app:

rails new test1
cd test1

Edit the Gemfile to add a Javascript engine. I use

gem 'therubyracer'

Then, see if you can run rake:

rake db:migrate

This should silently complete.
Then go back to your application and find what's missing.

Thanks

Bruce

Reply to this email directly or view it on GitHub:

#1 (comment)

@drew1two

I'm sure that's not the case in this instance though. I'm quite sure I'm
miss interpreting your instructions somehow or we genuinely are getting
this error at this step.

On Wed, Feb 22, 2012 at 6:07 PM, Drew Parker drewisdad@gmail.com wrote:

I am on win7 64bit. Maybe.... dunno.
I really have to look into every gem that looks kewl before I bundle
install them as so many use fork that damn windows dunno anything about.

On Wed, Feb 22, 2012 at 6:02 PM, Drew Parker drewisdad@gmail.com wrote:

I made the skeleton first yes. Then followed your instructions.

this is the content of the rakefile as you've prolly seen always

#!/usr/bin/env rake
# Add your own tasks in files placed in lib/tasks ending in .rake,
# for example lib/tasks/capistrano.rake, and they will automatically be
available to Rake.

*
*
require File.expand_path('../config/application', FILE)
*
*
Devise::Application.load_tasks

On Wed, Feb 22, 2012 at 5:42 PM, Bruce Perens <
reply@reply.github.com

wrote:

On 02/21/2012 10:35 PM, drew1two wrote:

Haha, sorry I confused you. the quoted part "Don't know how to build
task 'migrate'" is the Error I get when I run 'rake db:migrate.
My bad :)
It sounds like you don't have a Rakefile. When Rails creates a skeleton
application, it makes one. To test, make a new Rails app:

rails new test1
cd test1

Edit the Gemfile to add a Javascript engine. I use

gem 'therubyracer'

Then, see if you can run rake:

rake db:migrate

This should silently complete.
Then go back to your application and find what's missing.

Thanks

Bruce

Reply to this email directly or view it on GitHub:

#1 (comment)

@drew1two

Just thinkin outside the box for now. You wouldn't happen to have the
skeleton of the output of you generator somewhere I can use to get started
with? That would be great then you wouldn't have to look into something
that could (and prolly is) be my fault somehow.

Cheers again
Just great to see something using the latest and greatest, which I think
you got here.

On Wed, Feb 22, 2012 at 6:11 PM, Drew Parker drewisdad@gmail.com wrote:

I'm sure that's not the case in this instance though. I'm quite sure I'm
miss interpreting your instructions somehow or we genuinely are getting
this error at this step.

On Wed, Feb 22, 2012 at 6:07 PM, Drew Parker drewisdad@gmail.com wrote:

I am on win7 64bit. Maybe.... dunno.
I really have to look into every gem that looks kewl before I bundle
install them as so many use fork that damn windows dunno anything about.

On Wed, Feb 22, 2012 at 6:02 PM, Drew Parker drewisdad@gmail.com wrote:

I made the skeleton first yes. Then followed your instructions.

this is the content of the rakefile as you've prolly seen always

#!/usr/bin/env rake
# Add your own tasks in files placed in lib/tasks ending in .rake,
# for example lib/tasks/capistrano.rake, and they will automatically
be available to Rake.

*
*
require File.expand_path('../config/application', FILE)
*
*
Devise::Application.load_tasks

On Wed, Feb 22, 2012 at 5:42 PM, Bruce Perens <
reply@reply.github.com

wrote:

On 02/21/2012 10:35 PM, drew1two wrote:

Haha, sorry I confused you. the quoted part "Don't know how to
build
task 'migrate'" is the Error I get when I run 'rake db:migrate.
My bad :)
It sounds like you don't have a Rakefile. When Rails creates a skeleton
application, it makes one. To test, make a new Rails app:

rails new test1
cd test1

Edit the Gemfile to add a Javascript engine. I use

gem 'therubyracer'

Then, see if you can run rake:

rake db:migrate

This should silently complete.
Then go back to your application and find what's missing.

Thanks

Bruce

Reply to this email directly or view it on GitHub:

#1 (comment)

@BrucePerens
Owner

Add the -t or -v flags to rake and see if it tells you more.

 Thanks

 Bruce
@BrucePerens
Owner

On 02/21/2012 11:19 PM, drew1two wrote:

Just thinkin outside the box for now. You wouldn't happen to have the
skeleton of the output of you generator somewhere I can use to get started
with?
It doesn't make a skeleton, just runs code in its engine. This might be
a Windows issue, too. I am running Linux and have only tested on that.
However, I don't believe I am using fork or threads.

 Thanks

 Bruce
@drew1two

Ahhhh, therein lies my problem (I think). I was supposed to include your
code into MY rails skeleton as it's an Engine not a Generator. Haha If
it's that simple I'm the dumbest in the world...(quite possibly) . I've
only used generators before (2.3 weeks new now :) ).
Can you confirm for me that this is what I have to do (integrate your
Engine code) to make it work. I was executing your instructions from
within your codes Own directory sitting parallel with my skeleton.

On Wed, Feb 22, 2012 at 6:25 PM, Bruce Perens <
reply@reply.github.com

wrote:

On 02/21/2012 11:19 PM, drew1two wrote:

Just thinkin outside the box for now. You wouldn't happen to have the
skeleton of the output of you generator somewhere I can use to get
started
with?
It doesn't make a skeleton, just runs code in its engine. This might be
a Windows issue, too. I am running Linux and have only tested on that.
However, I don't believe I am using fork or threads.

Thanks

Bruce

Reply to this email directly or view it on GitHub:

#1 (comment)

@drew1two

Bruce,
You wouldn't know of a project that utilizes Devise, omniauth, CanCan,
using Rspec (not cucumber), all with the latest builds that has example
code I could follow?

On Wed, Feb 22, 2012 at 6:46 PM, Drew Parker drewisdad@gmail.com wrote:

Ahhhh, therein lies my problem (I think). I was supposed to include your
code into MY rails skeleton as it's an Engine not a Generator. Haha If
it's that simple I'm the dumbest in the world...(quite possibly) . I've
only used generators before (2.3 weeks new now :) ).
Can you confirm for me that this is what I have to do (integrate your
Engine code) to make it work. I was executing your instructions from
within your codes Own directory sitting parallel with my skeleton.

On Wed, Feb 22, 2012 at 6:25 PM, Bruce Perens <
reply@reply.github.com

wrote:

On 02/21/2012 11:19 PM, drew1two wrote:

Just thinkin outside the box for now. You wouldn't happen to have the
skeleton of the output of you generator somewhere I can use to get
started
with?
It doesn't make a skeleton, just runs code in its engine. This might be
a Windows issue, too. I am running Linux and have only tested on that.
However, I don't believe I am using fork or threads.

Thanks

Bruce

Reply to this email directly or view it on GitHub:

#1 (comment)

@BrucePerens
Owner

Yes, you just install the engine as a gem in the Gemfile, run bundle,
and then put the configuration file in your application and edit it there.

This is actually the only code in which I've ever used Devise. I've not
gotten to a role-based permission system like CanCan yet in the
application where I'm using it, so I can't help with that.

 Thanks

 Bruce

On 02/21/2012 11:46 PM, drew1two wrote:

Ahhhh, therein lies my problem (I think). I was supposed to include your
code into MY rails skeleton as it's an Engine not a Generator. Haha If
it's that simple I'm the dumbest in the world...(quite possibly) . I've
only used generators before (2.3 weeks new now :) ).
Can you confirm for me that this is what I have to do (integrate your
Engine code) to make it work. I was executing your instructions from
within your codes Own directory sitting parallel with my skeleton.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment