stuebinm
a2908a9f66
This is a first attempt to package octycs' keytracker [1] application. It's more a quick-and-dirty approach, so there are a couple things to note: - the config file is just generated by Nix as whatever the module got in its config option stuffed into a toml file. There are no default values, so all values must be set by hand – or rather, we just write the default values in the config. - I couldn't figure out how to actually make this thing work. It looks like it /should/ work, but gets hung up every time on loading key information via the web interface. Then again, it appears our current config on libocedrus also doesn't conform to what the readme says, so perhaps I just missed something that's as-yet undocumented. - The module just calls python instead of an actual server as backend. This is recommended just for development/testing, not actual deploys [2], but since the project is missing a setup.py which afaik are required to package these things more sensibly [3], that's it for now. - keys and corresponding tokens are currently baked into the nix store. This seems a bad idea, and I'll fix it as soon as I find the time. [1] https://gitlab.infra4future.de/octycs/keytracker [2] https://gitlab.infra4future.de/octycs/keytracker/-/blob/master/server/Readme.md [3] https://flask.palletsprojects.com/en/1.1.x/tutorial/deploy/
28 lines
573 B
Nix
28 lines
573 B
Nix
{ stdenv
|
|
, python38
|
|
, lib
|
|
, fetchgit
|
|
, ...}:
|
|
|
|
stdenv.mkDerivation rec {
|
|
pname = "keytracker";
|
|
version = "0.0.1";
|
|
|
|
src = (fetchgit {
|
|
url = "https://gitlab.infra4future.de/octycs/keytracker";
|
|
rev = "0a124c3e7bc5c0e840d45399ad5e69485bb3e49c";
|
|
sha256 = "1l3djg3qfisrvv9shi2p44h026n58pimwbvr2idjnaill688s1qf";
|
|
}).outPath + "/server";
|
|
|
|
buildPhase = ''
|
|
echo "${python38.withPackages(ps: with ps; [ flask ])}/bin/python $out/server.py" > wrapped
|
|
chmod +x wrapped
|
|
'';
|
|
|
|
python = true;
|
|
|
|
installPhase = ''
|
|
mkdir -p $out
|
|
cp -r * $out
|
|
'';
|
|
}
|