Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Postgresql: multiple instances, OpenSSL, flexible configuration #5271

Closed
wants to merge 3 commits into from
Closed

Postgresql: multiple instances, OpenSSL, flexible configuration #5271

wants to merge 3 commits into from

Conversation

ip1981
Copy link
Contributor

@ip1981 ip1981 commented Dec 9, 2014

No description provided.

@edolstra
Copy link
Member

edolstra commented Dec 9, 2014

I would prefer not to have two PostgreSQL modules. I would prefer changing the existing one to support multiple instances, e.g. by adding services.postgresql.instances and mapping services.postgresql.* to services.postgresql.instances.default if services.postgresql.enable == true.

@ip1981
Copy link
Contributor Author

ip1981 commented Dec 9, 2014

I would prefer to unsee the existing PostgreSQL module. But since it exists (and maybe is used somewhere), let it go gracefully.

@lucabrunox
Copy link
Contributor

@edolstra Rather than .instances I'd go straight for services.postgresql.<instance>, as with containers. The user would certainly get an error anyway from using e.g. services.postgresql.enable, so breaking the interface shouldn't be a big problem especially after 14.12 has been branched.

In addition, I'd like to suggest an helper function e.g. multipleInstances = serviceOpts: .... Many services like pgsql can benefit from this and have a consistent interface for all other services for free.
In fact, I'm tempted to have xserver.<instance> where instance would be the vt name.

@ip1981
Copy link
Contributor Author

ip1981 commented Dec 9, 2014

services.postgresql.<instance> makes sense.

@ip1981
Copy link
Contributor Author

ip1981 commented Dec 9, 2014

In addition, I'd like to suggest an helper function e.g. multipleInstances = serviceOpts: .... Many services like pgsql can benefit from this and have a consistent interface for all other services for free.

We need more services to design multipleInstances.

@lucabrunox
Copy link
Contributor

@ip1981 multipleInstances is very trivial and the interface is going to be like what I've described, there's no need to wait for other services to design it.

@edolstra
Copy link
Member

edolstra commented Dec 9, 2014

What's wrong with the existing module?

services.postgresql.<instance> is not possible because it is ambiguous (since it conflicts with existing option names).

@lucabrunox
Copy link
Contributor

@edolstra I'm talking about completely replacing the current module with services.postgresql.<instance>. Wrong, nothing. But I'd prefer if all the services would have this format.

@7c6f434c
Copy link
Member

7c6f434c commented Dec 9, 2014

@edolstra I'm talking about completely replacing the current module with services.postgresql.<instance>. Wrong, nothing. But I'd prefer if all the services would have this format.

This would need some convention for inter-service dependency, though.

@lucabrunox
Copy link
Contributor

@7c6f434c that's right

@lucabrunox
Copy link
Contributor

I've opened an issue here with a proposal of mkMultiInstance and also a problem: #6784

@jpierre03
Copy link
Contributor

(triage) @ip1981 @lethalman is there some news ?

@ip1981
Copy link
Contributor Author

ip1981 commented Jan 15, 2017

Nope. Not interested anymore. https://github.com/zalora/nixsap/tree/master/modules/apps/postgresql

@fpletz fpletz closed this Jan 15, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

8 participants