Home-Manager got first level support for calendars and contacts.
Provided integrations are vdirsync and khal which I'm already using.
I therefore migrate from my own setup to the upstream setup.
Issue on home-manager project:
https://github.com/nix-community/home-manager/issues/2335
Very basic, but maybe better then all the shiny none working solutions.
Will sync all calendars to vdir.
khal is able to parse and show them. khal also offers an cli interface
to fetch events for a certain time.
Properly use keepass xc via secret tool as command line tool
Enable keepassxc usage as secret tool.
Remove crypted file as this no longer keeps passwords
Remove korganizer as it doesn't provide notifications, try khal
I've added the following myself:
* mattermost
* purple-signald (waiting for https://github.com/NixOS/nixpkgs/issues/188384)
* purple-events
* purple-libnotify
and added slack from nixpkgs.
I'm also trying to make signal integration work.
Not sure whether I'll keep pidgin, as I expect video calls from within
slack not to work.
But would be cool to have a single open source messenger instead of x
instances of chromium as wrapper around closed source web applications.
Some apps use different sources.
I setup xresources and ensure there is only one icon theme (includes
cursor).
This uses the single source of truth, thanks to nix / home-manager.
Except snap packages, those still don't work.
Add new gtk configuration.
Use tmpfiles to provide the generated sources like themes to the system.
Also use for desktop files and remove old no longer needed readme entry.
Use home-manager to create xsession.
Readme contains info on how to start xsession on login.
That way home-manager can maintain languages, keyboard and further stuff
globally for user.
No more need to set stuff as workaround within i3 or zsh.
Also enabled to start systemd units after login, as home-manager will
create and trigger `hm-graphical-session.target`.
The module doesn't work or exist anymore.
I use a lightwight battery icon instead which I add as a service to
start during login.
And I don't need the wifi thingy.
Install and configure i3 via nix home-manager.
This commit just migrates existing configuration.
It doesn't clean things up, e.g. move stuff to expected locations.
I configure x* tools from within i3 right now …
Also didn't clean things up, e.g. sort and group related things.
I'm still on Ubuntu and use etckeeper to track changes to /etc.
This small script will push it to my own Gitea instance as a backup and
online history in case I need it.
Remove flakes for now.
I will use shells for now to not have a mixed setup.
Add composer v1 for a single customer project as overlay due to usage in
shell instead of flakes.
Adjust folder to not have unnecessary deep structure.
Add shell for reuter monorepo using composer v1.
Those were the last piece in my old .dotfiles repository.
The whole configuration is now defined here.
Only customer specifics are in a separate location / repo to not expose
any sensible data.
Looks like there was no pre build binary to use.
I therefore switched over to the snap package from Ubuntu.
My machine is not able to build Chromium :D
There is an existing module.
Existing manually written and linked files are replaced with usage of
the module.
This has the advantage that I don't need to know where to place the
files and which format to use.
Furthermore, the module will check whether I've typos in options and
whether values match expected types.
I managed my setup manually.
This commit ports the existing setup to home-manager.
The program module is used to install neovim together with plugins.
Custom plugins are now maintained at Gitea / GitHub and loaded via nix as well.
Place ctags configuration in expected location.
It wasn't loaded due to wrong location.
Do not add typescript as I'm not using typescript anymore on a
professional level.
Do not install package which won't work anyway.
Get out of the way for existing apt installed version.
Symlink whole applications folder to not update after each run.
Create dedicated xdg desktopEntries to start web apps.
Use chromium where necessary, e.g. due to audio / video experiences.
Start web apps with dedicated Firefox profiles.
Configure those profiles to hide any UI to have an actual app feeling.
Daniel Siepmann