* Fix wrong path for adding packages.
* Fix that custom package is no longer added via overlay.
* Fix upstream PR regarding new folder structure.
* Remove idea as I use git-crypt for now.
No need for overlays.
Instead create own packages and call them via callPackage.
That will keep them simpler and allows dependency injection.
I can follow existing patterns from nixpkgs, etc.
It pops up way to often.
Also looks like it doesn't integrate well if installed via nix.
Probably needs to be installed by actual OS for proper access.
This allows me to easily see which version updates happen between two
store paths (e.g. after updating)
Fetch store paths via `home-manager generations` and run `nvd diff
<old> <new>`
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`.
system tools are not possible and I stick to ubuntu as a host os.
In general I shouldn't care to much about the host OS.
I use nix for most things and will improve the situation.
Most customers also have ubuntu or debian systems as servers.
It is a good thing to have the same folder and software setup.
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.
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.
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.
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.
I created a private repository within `registries/customer-projects`.
This holds flakes.
The folder is registered as registry.
That allows to run the following from within a customer project:
nix run cp\#reuter-phpstan
In order to execute the customer specific application from flake.
The phps used via flake for local development of legacy projects
distributed pre build packages via cachix.
Install cachix and add configuration to allow fetching of pre compiled
packages.
The flake is very basic and encapsulates frontend compilation via node
for customer projects.
The flake is intended to be used by other flake.nix within the projects,
which will use the defined packages to build apps outputs.
They should use the packages like `writeShellApplication` itself,
call it with necessary argument set in order to receive a
out of the box working solution.
A template is also provided which can be used like:
nix flake init -t <path to this flake>
`defaultTemplate` is defined in output and will be used.
My host does no longer provide any node or npm or yarn.
Project are partially migrated to shell.nix already.
I still need to migrate all projects. But I'm not working to much on
frontend and don't need to re compile assets to often, so no worries.
Some stuff will not work anymore, e.g. coc within neovim needs nodejs.
That's broken for now, but I don't care to much, not sure whether I used
it at all.
That will be part of neovim migration to home-manager / nix.
I prefer restructured text, but Gitea has no out of the box support.
So switch to markdown as there is more or less no difference anyway,
for such a simple file.
One big downside: There is no definition list.