Hello Joey,
I am thinking to add a "Proxy" info to an host, the same way the Apt.proxy (and HostAptProxy) is working so that all services can (optionnally) tap into this information to setup their need for a http[s] proxy (eg. R, WordPress or other CMS/webapp...).
My idea is to write a 'Proxy.hs' module containing just the few functions to set up the host information (let name it HostProxy
), and use it throught a function withProxy
taking as argument a function (HostProxy -> Property w)
and will return a "Property w
"
Is this a reasonnable way to handle the need ? If I code such a module, would anyone else be interested and would such a solution be accepted on the upstream ? Otherwise what would you advise ?
Cheers, and thanks for Propellor !
Serge.
Me again.
To start testing, I have writen a minimal module :
In this version the
withProxy
is only handling the case of aDebianLike
property, whereas I should be able to have a more polymorphic signature akin :withProxy :: Desc -> (Maybe HostProxy -> Property a) -> Property a
But this does not work with the error message :
And I don't know how to provide the information to the compiler that
Property a
may be any type under theUnixLike
'metatype'