summaryrefslogtreecommitdiffstats
path: root/pkgs/servers/gotify
AgeCommit message (Collapse)Author
2021-01-23treewide: Remove usages of stdenv.lib by @doronbeharDoron Behar
Per: https://github.com/NixOS/nixpkgs/issues/108938
2021-01-11treewide: with stdenv.lib; in meta -> with lib;Profpatsch
Part of: https://github.com/NixOS/nixpkgs/issues/108938 meta = with stdenv.lib; is a widely used pattern. We want to slowly remove the `stdenv.lib` indirection and encourage people to use `lib` directly. Thus let’s start with the meta field. This used a rewriting script to mostly automatically replace all occurances of this pattern, and add the `lib` argument to the package header if it doesn’t exist yet. The script in its current form is available at https://cs.tvl.fyi/depot@2f807d7f141068d2d60676a89213eaa5353ca6e0/-/blob/users/Profpatsch/nixpkgs-rewriter/default.nix
2021-01-07gotify-server: 2.0.20 -> 2.0.21R. RyanTM
2020-11-30gotify-server: fix UI deliveryMaximilian Bosch
After bisecting `nixpkgs-master` I realized that the usage of `-trimpath`[0] by default for Go modules[1] is responsible for breaking UI delivery of `gotify-server`[2]. This behavior can only be turned off by setting `allowGoReference` to `true`. We may want to find a better long-term fix, but given that this only affects a leaf-package and actually fixes the problem, this is good enough for now. Fixes #105472 [0] https://golang.org/doc/go1.13#go-command [1] 4e9f7bbf8573d07f7b0c87d97c026cd4aad5a758 [2] https://hydra.nixos.org/build/131660876
2020-10-16gotify-server: 2.0.18 -> 2.0.20Maximilian Bosch
https://github.com/gotify/server/releases/tag/v2.0.19 https://github.com/gotify/server/releases/tag/v2.0.20
2020-09-13gotify-server: 2.0.17 -> 2.0.18Doron Behar
Use new line in printf calls of update.sh, so editor config CI check won't fail.
2020-09-12gotify-server: fix UIMaximilian Bosch
In version 2.0.15 `gotify` switched to `packr` at 2.x which is why the UI can't be served properly via HTTP and causes an empty 500 response and the following errors in `journald`: ``` 2020/09/12 19:18:33 [Recovery] 2020/09/12 - 19:18:33 panic recovered: GET / HTTP/1.1 Host: localhost:8080 Accept: */* User-Agent: curl/7.72.0 stat /home/ma27/Projects/ui/build/index.html: no such file or directory ``` This wasn't caught by the VM-test as it only tested the REST and push APIs. Using their internal `packr.go` script in our build as it's the case in the upstream build-system[1] fixes the issue. [1] https://github.com/gotify/server/pull/277/files#diff-b67911656ef5d18c4ae36cb6741b7965R48
2020-08-15buildGoModule: remove platform.all from packageszowoq
2020-08-10buildGoModule packages: set doCheck = falsezowoq
2020-07-23gotify-server: 2.0.16 -> 2.0.17Doron Behar
2020-05-15gotify: adapt update script to use vendor shaDoron Behar
2020-05-14go-modules: Update files to use vendorSha256Colin L Rice
2020-05-10gotify-server: 2.0.15 -> 2.0.16Doron Behar
2020-04-27gotify-server: 2.0.4 -> 2.0.5Doron Behar
Improved update script / procedure by getting all versions and shas needed to build it.
2020-03-27Revert "Merge pull request #83099 from marsam/fix-buildGoModule-packages-darwin"Jörg Thalheim
This reverts commit 4e6bf03504c9e09f067cc6dee6b5aeec43a1405c, reversing changes made to afd997aab6e9b7a322198092c7828d6c560ac06f. Instead we propagate those frameworks from the compiler again
2020-03-21gotify-server: fix build on darwinMario Rodas
2020-02-19gotify-server: 2.0.13 -> 2.0.14Doron Behar
2020-01-02gotify-server: 2.0.12 -> 2.0.13Maximilian Bosch
https://github.com/gotify/server/releases/tag/v2.0.13
2019-12-01gotify-server: 2.0.11 -> 2.0.12Doron Behar
2019-11-26gotify-server: 2.0.10 -> 2.0.11Doron Behar
2019-10-25gotify-server: init at 2.0.10Doron Behar