If a user passes both `config` and `extraConfig` to the `yabai` serivce,
the generated `yabairc` file is invalid. This is because we do not add a
newline separator when we concatenate the config string generated by
`toYabaiConfig cfg.config` with `cfg.extraConfig`.
This PR prepends a newline to `cfg.extraConfig` if it is non-empty so
that the resulting `yabairc` config is valid.
This is useful for redirecting some TLDs to the different addresses. For
example I use it to make all requests to `*.localhost` to be resolved to
loopback address which allows me to easily work and test services that
are relying on different domains.
This reverts commit fb0a1763f5.
Reason: this implementation of the module is outdated and broken.
We recommend to follow instructions in the web app or
https://docs.hercules-ci.com
The nix.useDaemon option enables using a multi-user install without
managing the nix installation with nix-darwin. The following checks
apply to both cases.
`initdb` expects to read the locale or SQL_ASCII environment
variable to determine the most appropriate character set.
Instead, offer a configuration option.
This configures the user that runs the garbage collector, particularly
useful for single-user installs. Otherwise it runs as root resulting in
permission issues afterwards.
As the default package is now emacs 26.1 and --daemon flag falls back to forking behaviour the recommended way is to use fg-daemon, see: lists.gnu.org/archive/html/emacs-devel/2016-11/msg00383.html, lists.gnu.org/archive/html/emacs-devel/2017-05/msg00861.html
Since the package contains both chunkwm (daemon) and chunc (client) the
daemon shouldn't really be in PATH by default. Usually libexec is used
for this, however this would break the current expression used by
people. This enables moving chunkc to a bin output for this purpose.
eg. 7ad4b4d23d
This can be overrided if necessary, but I don't see any reason the
nixpkgs package shouldn't be the default. It looks like this package
didn't exist when the service was created.
These options unintentionally used the deprecated string type, the
important difference between these is the fact that string merges by
default (similar to eg. lines) while str can only have a single value.
This makes the service start on demand when a client connects to the
daemon socket, instead of keeping it alive.
services.nix-daemon.enableSocketListener = true;
@cleverca found this bug in the declarative hooks config. Any shell
variables referenced in a hook script would get expanded by the hooks
directory builder.
Prevent variable expansion by quoting the here doc limit string.
