Building the installer needs postgres running?

[brian gibb]

Hi,

posting this on behalf of Sharath who has just applied to join the group...

we are building the installer, following the instructions at:

https://github.com/GreenplumChorus/chorus/wiki/Building-a-Package-for-Deployment

However, we hit a problem in that while building the API docs the process fails with an error indicating that it is trying to access postgres. There is nothing to suggest postgres should be running at this point... should it be? 

If we do start postgres the process gets a bit further, but then fails due to a missing role ('postgres_chorus') but no point investigating that if the answer to the above is no!

thanks 

Brian

[Gregg Van Hove]

Hey Brian,

You do need Postgres to be running to generate the API docs. If you don't have a postgres_chorus user, it sounds like you haven't run

> rake development:init

which will set this up for you. Let us know if you're having problems running that command.

-Gregg

--
You received this message because you are subscribed to the Google Groups "chorus-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chorus-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[brian gibb]

Thanks, 

I'll check with Sharath tomorrow, though I'm sure he will have run 

>rake development:init

but presumably something in his env isn't quite right. I suspect a file permission issue, so we'll investigate.

In the mean time it would be good to update the wiki page to say that you need to start postgres... is that the only thing that needs started?  

i.e. follow the dev setup instructions, up to and including

>rake development:init

then 

>$CHORUS_HOME/packaging/chorus_control.sh start postgres

before running

>RAILS_ENV=packaging bundle exec rake package:installer --trace

thanks  

Brian

[Charles Hansen]

Updating now