Factorise other configuration options #22
No reviewers
Labels
No labels
api service
blocked
bug
component: fediversity panel
component: nixops4
documentation
estimation high: >3d
estimation low: <2h
estimation mid: <8h
productisation
project-management
question
role: application developer
role: application operator
role: hosting provider
role: maintainer
security
technical debt
testing
type unclear
type: key result
type: objective
type: task
type: user story
user experience
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: fediversity/fediversity#22
Loading…
Add table
Reference in a new issue
No description provided.
Delete branch "factorise-other-config"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR builds on top of #21; it factorises the other options that are in common between all configurations.
@ -7,0 +16,4 @@system.stateVersion = "24.05"; # do not changenixpkgs.hostPlatform = mkDefault "x86_64-linux";## REVIEW: Do we actually need this?yes because then you can ditch passwords entirely. you already have authorization when getting logged in over SSH, why would you type random strings into your keyboard again?
I was wondering what security specialists thought about this. @koen said on Matrix that they very much dislike direct
rootSSH, but they were fine with password-less sudo, so let's keep this option then.@ -7,0 +21,4 @@nix.settings.trusted-users = [ "@wheel" ];environment.systemPackages = with pkgs; [my rant won't fix it, so this is not a change request, but for the record: everyone should just bring their own tools to the server via ssh, there's technically no need to clutter the config with some random preferences that will never age well.
there's a thing called sshrc that demonstrates the principle, but these days with Nix you can have your exact favorite environment, defined locally on each remote login via SSH. to my surprise, no one seems to have thought it through to write the handful lines of bash and Nix required for that, but in my humble opinion this is how it should be done.
I very much agree with all this, and I was not happy copying these packages, but I decided that it was easier to just refactor, and to discuss this later. I have started keeping track of this discussion in Fediversity/Fediversity#25.
@ -1,5 +1,3 @@{ lib, ... }:I recommend keeping
so it's clear at first glance that it's a module.
37b1cc01c4tofca563a987environment.systemPackagesininfra/common/default.nix#25