<feed xmlns='http://www.w3.org/2005/Atom'>
<title>depot/modules/flake-module.nix, branch master</title>
<subtitle>Unnamed repository; edit this file 'description' to name the repository.</subtitle>
<id>http://src.web.4kb.net/depot/atom/modules/flake-module.nix?h=master</id>
<link rel='self' href='http://src.web.4kb.net/depot/atom/modules/flake-module.nix?h=master'/>
<link rel='alternate' type='text/html' href='http://src.web.4kb.net/depot/'/>
<updated>2024-12-18T04:03:27Z</updated>
<entry>
<title>Push configuration out of flake</title>
<updated>2024-12-18T04:03:27Z</updated>
<author>
<name>Kleidi Bujari</name>
<email>mail@4kb.net</email>
</author>
<published>2024-12-18T04:03:27Z</published>
<link rel='alternate' type='text/html' href='http://src.web.4kb.net/depot/commit/?id=eb13a9a552f9e50a66faba985521ba8e3483c447'/>
<id>urn:sha1:eb13a9a552f9e50a66faba985521ba8e3483c447</id>
<content type='text'>
Projects are not necessarily all exported by the system flake, and
should freely support other derivations. The new "mod" directory will be
used for most projects, and it can be imported by machine
configurations.

That said, the tooling around flakes is pretty good and will still be
used until the dependency is lessened.
</content>
</entry>
<entry>
<title>Initial scaffolding and layout</title>
<updated>2024-11-23T21:36:43Z</updated>
<author>
<name>Kleidi Bujari</name>
<email>mail@4kb.net</email>
</author>
<published>2024-11-23T21:36:43Z</published>
<link rel='alternate' type='text/html' href='http://src.web.4kb.net/depot/commit/?id=3ccc7e784a0ed5b19910ab856f6d9774a6f27956'/>
<id>urn:sha1:3ccc7e784a0ed5b19910ab856f6d9774a6f27956</id>
<content type='text'>
Set up the modules of the flake. At this time, the flake is split into
modules and machines. Considering that additional top-level sections --
such as packages and shells -- will also be added, it might make sense
to keep all nix related things in one top-level directory, alongside the
flake.nix file.

This is all under the assumption that later amendments to the project
will introduce other tech, such as terraform.
</content>
</entry>
</feed>
