The build script doesn't pass the correct path to nixpkgs in the nix-build
invocation, which causes build failures outside a standard libkookie-booted
environment.
>From jq(1):
o --raw-output / -r:
With this option, if the filter´s result is a string then it will be
written directly to standard output rather than being formatted as a
JSON string with quotes. This can be useful for making jq filters talk to
non-JSON-based systems.
This commit reverts the following commits:
* b2681a59d5.
* a35411dc74.
As already mentioned in the commit message of a2513a, this design
decision turned out to be a bad one: instead of having the iterator
abstraction branch internally, an API is required to control the flow
of iterators externally. This way users can opt-into complexity,
instead of having to opt-out.
I opted to revert the commits, instead of trying to untangle all the
changes made in these two commits, to avoid breaking any of the code.
Signed-off-by: Katharina Fey <kookie@spacekookie.de>
Previously a Yield object was either a file dump, or a simple
enumeration on a directories children, with no associated type state
for them. This commit implements a mechanism to internally fetch this
type information, to pass out to a user via the Yield type.
This way it is much easier to figure out which entries are
directories, and which are files. Additional queries have to be
passed into the FileTree for lookups. In a way, this commit gives up
on the idea of having a nested API structure for the time being, until
constructing sub-FileTrees becomes a real necessity
By default in Nginx, if you want to override a single fastcgi_param,
you have to override all of them. This is less of a big deal if
you're editing the Nginx configuration directly, but when you're
generating the Nginx configuration with Nix it can be very annoying to
bloat your configuration repeating the default values of FastCGI
parameters every time.
This patch adds a fastcgiParams option to Nginx locations. If any
parameters are set through this, all the default values will be
included as well, so only the ones that are changing need to be
supplied. There's no way to use fastcgiParams to actually override
all parameters if that's what you want, but I think that's a niche use
case and it's still possible using extraConfig, which up until now was
the only option
Nginx allows the fastcgi_param directive in http and server scopes as
well as location, but here I only support location. It would be
possible to support the others, but I don't think it's worth it. It
would be a possible future enhancement if somebody has a need for it.
This is required for emacs lsp to pick up where to set the root
directory for language server daemons. Ideally, a future monorepo
utility (such as nom) would create .projectile files automatically
when creating a new project in the tree.
Katharina Fey
Artemis Tosini