Commit graph

13 commits

Author SHA1 Message Date
319f827aa0
add new key for stuebinm 2022-11-13 20:22:23 +01:00
380934299b niv: remove home-manager
(not used for anything atm)
2022-11-11 16:30:38 +01:00
13b81b37f4 users.nix: re-add hexchen's ssh keys
(these were previously defined via nix-hexchen)
2022-11-11 16:30:38 +01:00
daac7ebcb0 remove users/hexchen.nix 2022-11-11 16:30:38 +01:00
3ea537459b
change name 2022-09-12 19:29:51 +02:00
schweby
3dc6b5e3e9
common/users: update schwebys ssh key 2022-05-22 15:08:42 +02:00
schweby
1064836092
Revert "security: remove hexchen"
This reverts commit bab826b1c7.
Also fixes hexchen nix due new logic
2021-03-26 22:04:27 +01:00
schweby
bab826b1c7 security: remove hexchen 2021-03-12 23:53:51 +01:00
schweby
db51a3adde common: set schweby's shell to fish 2021-03-12 12:28:26 +01:00
hexchen
c36eb51ff4 Revert 43d36bb3d7
This is a partial revert, reintroducing hexchen to the project.
As it turns out, I am still quite invested in the project and require
frequent access to the nix-based infrastructure.
2021-02-11 18:59:10 +00:00
hexchen
43d36bb3d7 remove hexchen from the project
I am no longer comfortable with putting resources into this project and
therefore request to be removed from all infrastructure. I am still
happy to help out with software I set up, but I will no longer actively
maintain any services. As far as possible, I will remove myself from all
access groups or other privileged positions related to this project.

Essentially, I'm stepping down as a maintainer. I still reserve the
right to make changes via the established change processes (Merge
Requests as well as Issues in the meta-repositories), but I will no
longer make direct changes to infrastructure without going through those
review processes.
2021-01-25 11:37:34 +00:00
hexchen
b288102f76 common/users: import hex-nix to deduplicate config 2021-01-11 00:30:08 +00:00
hexchen
851052014a complete restructure of haccfiles
here be winkekatzen
2021-01-10 23:53:41 +00:00
Renamed from configuration/common/users.nix (Browse further)