summaryrefslogtreecommitdiff
path: root/stack.yaml (follow)
Commit message (Collapse)AuthorAgeFilesLines
* a year went byHEADmainstuebinm2023-10-241-36/+0
| | | | | | | | | | | | | This does many meta-things, but changes no functionality: - get rid of stack, and use just cabal with a stackage snapshot instead (why did I ever think stack was a good idea?) - update the stackage snapshot to something halfway recent - thus making builds work on nixpkgs-23.05 (current stable) - separating out packages into their own cabal files - use the GHC2021 set of extensions as default - very slight code changes to make things build again - update readme accordingly - stylish-haskell run
* update stack resolverstuebinm2022-10-111-16/+5
| | | | | (also got rid of the map templater, which had version problems with mustache — it's not likely anyone will need it anyways)
* server: websocket for updates & auto-reloadstuebinm2022-03-191-0/+1
| | | | todo: find a better solution than writing javascript in haskell strings. SERIOUSLY.
* cwality-maps: add mustache templatingstuebinm2022-03-191-0/+2
| | | | | not going to be my faviourite templating language, but it seems to work pretty well for this.
* server: switch to universum prelude, some cleanupstuebinm2022-03-191-1/+1
| | | | it's slightly less of a mess than it was before
* add haskell.nix build systemstuebinm2022-03-191-2/+1
| | | | | | it's an annoying blockchain company, but apparently that thing is the only usable option to build stack things with nix without having to redefine all the (outdated) haskell packages in nixpkgs?
* server: simple servant-lucid stuffstuebinm2022-03-191-1/+1
|
* basic server setup (using servant)stuebinm2022-03-191-0/+12
| | | | | | | adds a very basic http server that can be sent links to repositories & will download & lint them, then answer the request with the lints. Should probably do this in a non-blocking way …
* use hpack and clean up modulesstuebinm2022-03-191-45/+1
| | | | as annoying as yaml is, cabal's package format is somehow worse, apparently
* playing around with typesstuebinm2022-03-191-0/+1
|
* build with stack & use newer Aesonstuebinm2021-11-141-0/+76
since the older versions of Aeson can be attacked via hash-flooding.