| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| ... | |
| |
|
|
|
|
| |
The goal is to be able to have multiple weechat services on one
machine, so a bunch of people can run their weechat clients under
different service users.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
| |
I had a clash between the base config and my workstation, which lead
to `git send-email` not being available because `git` (minimal) was
shadowing `gitFull`.
|
| |
|
|
|
| |
External keyboards never keep the speed I set. I don’t want that. I
don’t want to interact with udev, either.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The general consensus seems to be to use
vuizvui.user.<username>.<category>.<module name>
instead of
vuizvui.<category>.<user name>.<module name>
Things done to test this change:
* Checked build of machines.profpatsch.legosi.build
* Checked evaluation of machines.profpatsch.shiki.build
|
| |
|
|
|
| |
This should backup every service in `/var/lib` and anything I add in
the future that I might have missed.
|
| |
|
|
|
|
|
|
|
|
| |
Previously I had actually rebuilt the system locally, but since I use
the deploy script, I don’t need to have a full up-to-date nixpkgs
checkout, and only copy over the system closure.
Thus, set the path to only contain nixpkgs, and only a link to the
latest github unstable tarball in case I really need it e.g. for a nix
shell.
|
| |
|
|
|
|
| |
Before we just set 50M on workstations, but let’s increase to 500M and
set it as default on every machine, so we don’t run out of space
because somebody DDoSes our server logs.
|
| |
|
|
| |
Small script to deploy my machines.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Dumb wrapper around `nix-instantiate` for something I often need.
|
| | |
|
| |
|
|
|
|
|
|
|
| |
Small tool which takes a block of nix options that should produce a
script to run, and then calls the script with the rest of argv
e nix-run { -A foobar } a b c
calls `nix-build -A foobar && ./result a b c`.
|
| |
|
|
|
|
|
|
|
|
| |
This is a working PoC of specifying module configs as toml
configuration with simple to understand semantics.
Both the option definitions and the actual config values can be
specified via the toml DSL.
This is extremely happy-path for now, so errors are gonna be horrible.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Often times I want to execute “block-style” programs directly, but it
is rather inconvenient to type out `execlineb -c "…"` every time, plus
-c wants the argv as a single string instead of an argv.
The alternative, using the block representation with leading spaces,
is even less ergonomic.
So instead of
execlineb -c "nix-run { -A pkgs.profpatsch.e ~/vuizvui } echo hello"
or even
nix-run ' -A' ' pkgs.profpatsch.e' ' /home/me/vuizvui' '' echo hello
I can now write
e nix-run { -A pkgs.profpatsch.e ~/vuizvui } echo hello
and it will work as expected (provided your shell expands inside {}
blocks, which bash does but fish doesn’t for some reason).
If no argument is passed, e falls back to opening a shell prompt.
|
| |
|
|
|
|
|
|
|
| |
alock is really bad locking software. It is slow, it becomes
transparent, it even crashes sometimes. All the things a good lock
screen should never do.
i3lock is the trusted “standard” featureless locksceen, so this switch
has been procrastinated for way too long.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This was one of the places where types.loaOf was still in place and it
got removed a while[1] ago and this in turn causes evaluation to fail
for quite a few machines:
The option value `boot.initrd.luks.devices' in `...' is not of type
`attribute set of submodules'.
I've not only changed all the machines to use attribute sets but also
fixed the check in core/tests.nix, because comparing against a list when
the actual type is an attribute set will result in all the LUKS tests to
be part of *all* channels, no matter whether you're actually using LUKS.
[1]: https://github.com/NixOS/nixpkgs/commit/20d491a317d9956ddca80913f07
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
Cc: @sternenseemann
|
| |
|
|
|
|
|
|
|
|
|
|
| |
This is a step towards a saner deployment for these machines.
The NIX_PATH is fixed, so that everything on the running system always
uses exactly the nixpkgs version the system was deployed with.
The deployment is done by copying the system closure and switching to
it via the `bin/switch-to-configuration` script.
Uses the reference to pkgs.path, and applies filterSourceGitignore on
the directory, since I often deploy from a local checkout which is
half a GB without the gitignore filter.
|
| |
|
|
| |
used for access to /data/seeding
|
| | |
|
| |
|
|
|
|
| |
Explicitely set default fonts for (sans)serif, monospace and emoji.
Add Noto Color Emoji as emoji font.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Also add the service to legosi so I can use it from the weechat user.
|
| | |
|
| |
|
|
| |
No libpurple for just XMPP, phew.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
While it's fine to use <nixpkgs> on most systems, we deliberately want
to avoid the use of <nixpkgs> to make sure that whenever we for example
run <nixpkgs/nixos/lib/eval-config.nix> with a custom "pkgs" argument we
are guaranteed that we get the version we specify.
So this is one of the reason I used <nixpkgsSrc> on Hydra instead of
<nixpkgs>, so that whenever we have such occasions where we can't
guarantee such things, the evaluation will fail.
And right now, it does:
in job 'machines.profpatsch.legosi':
file 'nixpkgs/nixos/modules/profiles/qemu-guest.nix' was not found in
the Nix search path (add it using $NIX_PATH or -I), at
.../machines/profpatsch/legosi.nix:12:5
Fortunately, there is modulesPath, which refers to
<nixpkgs/nixos/modules> of the nixpkgs version passed via "pkgs".
Signed-off-by: aszlig <aszlig@nix.build>
Cc: @Profpatsch
|
| |
|
|
| |
Small Hetzner qemu virtual server.
|
| | |
|
