| Commit message (Collapse) | Author | Age |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Co-authored-by: Silas Schöffel <sils@sils.li>
|
| |
|
|
|
|
| |
With it, the service names become nearly illegible.
|
|
|
|
|
|
| |
The redirects always have an implicit dependency on the DNS config of
the running host. As such, simply stating them for all host is never a
possibility and setting them per host the only viable option.
|
| |
|
|
|
|
|
| |
Otherwise, this user's/group's owned files/directories could change when
a new user is added or removed, as we do not persist `/var/lib/nixos`.
|
|
|
|
| |
This allows us to avoid persisting `/var/lib/nixos`.
|
|
|
|
|
|
| |
Additionally, I've changed to owner of the `/var/lib/fail2ban` directory
to `root:root` as the main `fail2ban` service also runs under `root` and a
`fail2ban` user is never created.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Persisting them, without marking the `/srv` containing fs as
`neededForBoot` will result in a kernel panic in the init (because
`impermanence` tries to mount these directories and fails as `/srv` is
still missing.)
Thus, each host, that sets `/srv` to `neededForBoot` should add these
directories to `vhack.persist.directories`.
|
| |
|
|
|
|
|
| |
This avoids having to create them manually on the server and is,
overall just generally a better way to solve this problem.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
Commands in parentheses (i.e., `()`) are _subshells_ and `exit`ting from
these will not result in an `exit` of the actually _shell_. Thus, we use
want simple command grouping and use the correct syntax for that.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
The old `libreddit` subdomain still has redirection to avoid this
being a breaking change. But keeping the old subdomain is rather weird
considering their new name.
|
|
|
|
| |
This also includes a rename into `redlib` because of upstream changes.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
This option was newly added, as previously only on `fcgiwrap` instance
was run as root. We probably have not been affected by this, as our
`fcgiwrap` instance was already running as `git:nginx`.
Usage of the new options seems better either way, as they provide a
finer grained control over the user _each_ `fcgiwrap`ped service is
running at.
The security advisory: https://discourse.nixos.org/t/51419
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Take for example a repository name like: `some/organisation/project_a/team_c/repo_b`.
Setting the setting to `-1` means that cgit traverses the path from left
to right, until it has found 1 element (and `section-from-path` (or n
for short)is 0, because n is incremented after each iteration). E.g. :
~ [n=-1]
starting point: `some/organisation/project_a/team_c/repo_b`
~ [n=0]
after the first iteration: `some/organisation/project_a/team_c/repo_b`
Now `some/organisation/project_a/team_c` becomes the section, whilst
`repo_b` becomes the repo name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cgit effectively splits the repo path on '/' and then takes
`section-from-path` segments, which form the section. A negative value
here results in cgit traversing the path from left to right instead of
right to left. Beware that cgit only sets the section, if the path
contains `section-from-path` or more slashes in it (thus rendering this
setting defunct with the previous value of 1000).
There seems to be no way to tell cgit to always use all components up-to
the second to last for the section name, thus requiring all projects
that need a longer than 1 section length to set the `cgit.section`
git config variable via gitolite.
|
|
|
|
|
|
|
|
| |
The previously set variable is only used in the gitolite.conf file for
the `config` specifications on each repo. We can't use that because we
use "wild-repos". Thus we need to add the `user-configs` option to each
repo, allow users to change the git settings specified there with a
simple `ssh git@git.vhack.eu config <repo> --set cgit.owner <name>`.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
A lot of the added settings here have been tested. They will get
get tests to ensure they stay working, in later commits.
|
| |
|
| |
|
|
|
|
|
| |
Nix-sync was sort-of mixed into the nginx configuration, thus separating
it completely seemed reasonable.
|
| |
|
|
|
|
|
| |
This enables reviewed registration, assigns quota to new users and
enables manual approval of new videos.
|