summaryrefslogtreecommitdiff
path: root/server/Main.hs (unfollow)
Commit message (Collapse)AuthorFilesLines
2022-02-17server: remove a thunk leakstuebinm1-15/+13
(really a lot of these data structures should be eagerly evaluated into normal form, i suspect there's still a lot to be gained)
2022-02-16server: exneuland wants a token, apparentlystuebinm1-13/+7
2022-02-16server: post map updates to exneuland's APIstuebinm1-11/+44
2022-02-16server: remove cli-git, cli-extrasstuebinm1-4/+4
both these packages are hard to use, seem to be either unfinished or abandoned, and also generally not very good. Also for some reason they depend on `lens`. Removing them dramatically shrunk the dependency closure!
2022-02-16server: add mapservice GET endpointstuebinm1-4/+9
2022-02-16internal state: sort according to orgstuebinm1-5/+8
(also, more lenses i guess)
2022-02-16server: repositores & orgs fixed in configstuebinm1-62/+60
a very simple setup that might be usable for divoc and similar small events
2022-02-16… several hours of fighting with TOML laterstuebinm1-12/+16
WHO THOUGHT THIS SYNTAX WAS A GOOD IDEA?? (and who decided to write the least obvious combinator library to parse it?)
2022-02-15server: switch to universum prelude, some cleanupstuebinm1-51/+49
it's slightly less of a mess than it was before
2022-02-12server: added (somewhat) sensible loggingstuebinm1-20/+34
it's not very sensible, but at least it exists
2022-02-11server: more debug outputstuebinm1-1/+1
2022-02-11server: admin interfacestuebinm1-4/+10
(for now, just a list of all maps and their current status)
2022-02-10server: simple servant-lucid stuffstuebinm1-7/+18
2022-02-07server: simple toml configstuebinm1-3/+2
2022-02-07server: proper job handlingstuebinm1-18/+24
Note: the server will not check submissions for duplicates! (nor does it do any kind of rate-limiting)
2022-02-07non-blocking serverstuebinm1-24/+21
2022-02-01basic server setup (using servant)stuebinm1-0/+74
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 …