aboutsummaryrefslogtreecommitdiff
path: root/users/fcuny/default.nix (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-10-27ref(users/fcuny): and just like that ...Franck Cuny1-5/+0
2022-10-05ref(fcuny/notes): delete notesFranck Cuny1-2/+0
The notes are at https://github.com/fcuny/notes.fcuny.net
2022-10-05ref(fcuny/blog): delete the blogFranck Cuny1-2/+0
The blog moved back to https://github.com/fcuny/fcuny.net
2022-08-06ref(flake): tools and users packages are managed the same wayFranck Cuny1-0/+9
Configure the way we import these packages the same way, that way it's consistent and easy to use. Change-Id: I0e218f8fe9dd4cd2045bfee11c80de84ff769fe1 Reviewed-on: https://cl.fcuny.net/c/world/+/703 Tested-by: CI Reviewed-by: Franck Cuny <franck@fcuny.net>
2022-04-09add a few more modules to home/ and delete stuffFranck Cuny1-15/+0
2022-04-08delete all devel modulesFranck Cuny1-1/+1
They are all under home/ now
2022-04-08remove old 'trusted' modulesFranck Cuny1-2/+1
All of them are now under home/
2022-04-03home-manager: add `isTrusted`Franck Cuny1-2/+3
Install and configure some programs only on trusted machines. On trusted machines, my mails, GPG and a few other things are configured. A machine where this is not needed on a regular basis to get things done don't need that much information. Also rename `desktop/trust` to `trusted`, in case we want these packages on a host that is not a desktop, and `trusted` is a better description.
2022-04-03rename `desktop` to `isDesktop`Franck Cuny1-4/+2
The variable is used to define the kind of machine we're managing. `isDesktop` is a bit more descriptive. We import `devel` for all machines, and we fine tune which packages we want to install based on the value of `isDesktop`.
2022-03-04home: switch to emacsclient for EDITORFranck Cuny1-1/+2
2022-02-21devel: create new directory for devel modulesFranck Cuny1-1/+1
Add python, and move go from the cli modules. Install these modules only if we're a "desktop".
2022-02-12home-manager: re-organize configuration for myselfFranck Cuny1-16/+5
2022-02-12home-manager: remove trailing slashFranck Cuny1-1/+1
2022-02-12home-manager: start to organize user configurationFranck Cuny1-1/+1
2022-02-10home-manager: install password-storeFranck Cuny1-0/+1
2022-02-10users: we need to include desktop tooFranck Cuny1-0/+1
2022-02-10users: rename common.nix to default.nixFranck Cuny1-0/+0
We will use the variable 'destkop' to decide what to install after that.
2022-02-10users: enable home-manager for myselfFranck Cuny1-0/+3
2022-02-09home-manager: expand zsh configurationFranck Cuny1-0/+1
2022-02-09home-manager: add tmux configurationFranck Cuny1-0/+1
2022-02-09home-manager: fix one more typoFranck Cuny1-1/+1
2022-02-09home-manager: fix some typosFranck Cuny1-1/+1
2022-02-09home-manager: add more common programsFranck Cuny1-4/+4
Add git configuration and move go to its own module.
2022-02-09home-manager: fix typoFranck Cuny1-1/+1
2022-02-09home-manager: simplify the configurationFranck Cuny1-15/+1
I'm still struggling with documentation, and I'd rather have something simple that works rather than smart and does not work. The configuration for the host imports the modules that are relevant to that host (in the case of carmel, desktop and systems). For the home-manager, I create a profile "desktop" that contains stuff related to a desktop (i3, etc), and it includes the module "common" that contains stuff that I want on any machines (so that in the future, for a machine that is a server, the home manager will only import "common").
2022-02-08i3: move configuration to home-managerFranck Cuny1-0/+4
2022-02-08users: enable xdgFranck Cuny1-0/+2
2022-02-08home-manager: typo in my configFranck Cuny1-1/+1
2022-02-08home: initial configuration for home managerFranck Cuny1-0/+28