search

computerlyrik / chef-liquid-feedback

Chef cookbook for setting up a liquid feedback server | Category: Applications
3 stars 1 forks source link

split postgresql in resource #2

Open clkao opened 11 years ago

clkao commented 11 years ago

if a lf resource is defined with postgres host, we should skip setting up postgresql resources entirely.

(for example i found that heroku postgres is perfectly capable of running lqfb, and would like to configure my instance to use it)

computerlyrik commented 11 years ago

Which attributes are required if used on heroku?

computerlyrik commented 11 years ago

Which attributes are required if used on heroku?

clkao commented 11 years ago

i assume by explicitly defining external postgresql host and dbname in either the node or resource should mean the user is taking care of the pg configuration, and the resource should probably bypass db creation and just do the import bits

computerlyrik commented 11 years ago

Ok. I get your point about cleaning the resource from most postgres code.

Do you have any experience with executing "CREATE LANGUAGE plpgsql" as normal user (not postgres user)?

Also, database import is tied to database creation. Import will fail or act unpredictable if executed more often than once, after database creation. Any clue how to fix this?

clkao commented 11 years ago

i think with newer postgresql, we can do:

CREATE EXTENSION IF NOT EXISTS plpgsql

for import after creation, perhaps subscribing the postgresql_database resource? I am not very familiar with the database recipes though.