Hiya - back in hobo land after working on some other stuff for a while.
I wanted to set up a new project to use Postgres. Planning to run on
Heroku, so having my dev DB the same as the intended target will perhaps
avoid all those "database agnostic" problems ;)
I'm using rvm. Set up new Ruby 2.0.0-p401, and rails 4.0.5 to use with hobo
2.1
I running on a Mac and have a new Postgres.app running (9.3.4).
$ hobo new projectname -d postgresql
(lots of stuff about themes and front ends, etc)...
Initial Migration: [s]kip, [g]enerate migration file only, generate and
[m]igrate: [s|g|m] m
=> "m"
Migrating...
rake db:setup
FATAL: role "projectname" does not exist
Looks to me as though a pre-requisite for correct operation is to create a
new user ID for Postgres, so that the script completes.
Oddly, I have set up a different project, using the default sqlite3, and
then altered the config/database.yaml file to say I was using Postgres.
That, annoyingly, works. Or I don't know what's missing when I do it that
way. :)
If I create the user ID in Postgres beforehand and give it permission to
create databases, then "hobo new projectname -d postgresql" seems to run to
completion with no problems.
$ createuser -d projectname
Perhaps the hobo script should be modified to test for the existence of the
username, and to prompt to create one?
Or perhaps there should be some earlier note or check, before the script
bails. :)
Thanks for all the work on Hobo. It's an amazing piece of code.
--
You received this message because you are subscribed to the Google Groups "Hobo
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/hobousers.
For more options, visit https://groups.google.com/d/optout.
