init keytracker on hainich.
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/
2021-03-15 14:08:45 +00:00
|
|
|
{ stdenv
|
|
|
|
|
, fetchgit
|
|
|
|
|
, ...}:
|
|
|
|
|
|
|
|
|
|
stdenv.mkDerivation rec {
|
|
|
|
|
pname = "keytracker-frontend";
|
|
|
|
|
version = "0.0.1";
|
|
|
|
|
|
|
|
|
|
src = (fetchgit {
|
|
|
|
|
url = "https://gitlab.infra4future.de/octycs/keytracker";
|
2021-03-24 23:00:33 +00:00
|
|
|
rev = "2e83366913732029e8a5913f121df969172244ed";
|
|
|
|
|
sha256 = "sha256-ty8m/ITR2gmui3dIJX04FkGT/9SGuirrALyWaNaNwhE=";
|
init keytracker on hainich.
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/
2021-03-15 14:08:45 +00:00
|
|
|
}).outPath + "/frontend";
|
|
|
|
|
|
2021-03-24 23:00:33 +00:00
|
|
|
apiUrl = "http://chaski.stuebinm.eu:3030";
|
init keytracker on hainich.
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/
2021-03-15 14:08:45 +00:00
|
|
|
|
|
|
|
|
buildPhase = ''
|
|
|
|
|
substituteInPlace assets/main.js --replace "http://localhost:5000" $apiUrl
|
|
|
|
|
rm Readme.md
|
|
|
|
|
'';
|
|
|
|
|
|
|
|
|
|
installPhase = ''
|
|
|
|
|
mkdir -p $out
|
|
|
|
|
cp -r * $out
|
|
|
|
|
'';
|
|
|
|
|
}
|