Synthetica has quit [Quit: Connection closed for inactivity]
_ris has quit [Ping timeout: 268 seconds]
<disasm>
FRidh: thanks!
<disasm>
so 60k builds, another 3 days
<disasm>
so whats previous practice here. Do we fprk 19.09 off and merge staging-next into both or wait for hydra?
<disasm>
fpletz globin samueldr sphalerite ^^
<samueldr>
I don't think I've had to wait on staging when releasing
<samueldr>
though I think that the less divergence there is with nixos-unstable and nixos-19.09 at the release (in the following weeks) the better it is
<samueldr>
especially during zhf (zero hydra failures), if backports are harder to merge back, it's going to be a chore
<samueldr>
(I have no idea what the gcc8 changes include)
justanotheruser has quit [Ping timeout: 264 seconds]
justanotheruser has joined #nixos-dev
ixxie has quit [Ping timeout: 246 seconds]
FRidh2 has joined #nixos-dev
ixxie has joined #nixos-dev
FRidh2 has quit [Quit: Konversation terminated!]
cransom has quit [Quit: WeeChat 2.4]
justanotheruser has quit [Ping timeout: 245 seconds]
justanotheruser has joined #nixos-dev
_ris has joined #nixos-dev
__monty__ has joined #nixos-dev
jtojnar has joined #nixos-dev
jtojnar has quit [Ping timeout: 244 seconds]
jtojnar_ has joined #nixos-dev
obadz has joined #nixos-dev
FRidh2 has joined #nixos-dev
<teto>
I would like to transfer luarocks-nix to nixos-community, is that of interest ? who should I speak to ?
<andi->
teto: there are a bunch of people with access to it. adisbladis and zimbatm did a bunch of stuff there. Not sure how that happened to be and who they had to talk to.
<{^_^}>
teto/luarocks#6 (by teto, 39 minutes ago, open): transfer repo to nix-community
<adisbladis>
Ok, I'll ping you when I get back home and see if you're still awake
ixxie has quit [Ping timeout: 245 seconds]
ixxie has joined #nixos-dev
<infinisil>
I'm currently packaging a web server, it's listening to some port
<infinisil>
What do you think would be the optimal option to expose for configuring how it can be accessed?
<infinisil>
There's different ways of doing that. For one you can directly open the port, but alternatively you can run a web server in front of it that just proxies to the local port
<infinisil>
And then there's different web servers for that one could use
<infinisil>
I could have a separate option for each of those, but that doesn't feel right and bloats the module
<averell>
i like when SSL can be proxied (because you'll never match nginx featureset, basic auth, etc) without pain. So for example forcing protocol or it understands X-Forwarded-Proto and related.
<infinisil>
So that's an argument for providing nginx integration?
<infinisil>
averell: ^
<infinisil>
Maybe an option like `open = mkOption { type = nullOr (listOf (enum [ "open-local-port" "nginx" "httpd" ])); }` where `open = null` is the default and doesn't do anything, or you can select a set of values to enable, e.g. `open = [ "open-local-port" "nginx" ]`
<averell>
maybe, if that's as easy. i can set up the virtualhost/backend myself, but i'll want to reuse certificates, or put it in a subdirectory of some other virtual host etc.
<infinisil>
Yeah the implementation is rather easy
<infinisil>
I'm more asking about how to expose this to the user in a concise but useful way
<infinisil>
I like the enum thing, but using lists to represent a set is a bit out of place
<infinisil>
and once turned on it can't be turned off again, so that's no good
<infinisil>
I guess what I'll do is provide only nginx integration, it's what I'll be using, and what most people probably want to use
<infinisil>
Also, nginx can be used as a replacement for opening the port directly
<infinisil>
Yeah I like that
<infinisil>
I'll call it `nginxIntegration`, or maybe just `nginx`
<averell>
most people would think the other way around, but ok :)
<infinisil>
averell: You mean most people would want to use the port directly?
<averell>
i'm not sure, but at least most would think wrapping a port with nginx is natural.