| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
|
|
|
|
ChangeLog: https://github.com/gotify/server/releases/tag/v2.0.22
ChangeLog: https://github.com/gotify/server/releases/tag/v2.0.23
ChangeLog: https://github.com/gotify/server/releases/tag/v2.1.0
While the update only contains a few small features and a few bugfixes,
the change was rather messy for us unfortunately:
* It seems as if `npmjs.org`-packages can't be transformed into
`pkg___pkg-x.y.z` for Yarn's offline cache. The name
`https___registry.npmjs.org_caniuse_lite___caniuse_lite_1.0.30001237.tgz`
isn't the problem because when changing the URL "parser" of `yarn2nix`
to transform this into `org_caniuse_lite___caniuse_lite_1.0.30001237`
this doesn't help either.
Instead, I derived the fix from `gitlab`[1] where `yarn.lock` gets
patched to make sure that it detects the package in the offline-cache
properly.
* The frontend is now built with `react-scripts`. This is a problem for
us because it tries to write into `node_modules/.cache` even though
`node_modules` is a store-path in the context of `yarn2nix`[2].
The change isn't pretty, but solves the issue for us.
[1] https://github.com/NixOS/nixpkgs/blob/f007b794c758000a275b00dd0695d2fb155195f0/pkgs/applications/version-management/gitlab/default.nix#L85-L86
[2] https://github.com/facebook/create-react-app/issues/11263
|
|
|
|
This has been synonymous for ~5y.
Note that many of these runCommand bindings are unused, but that's
ok for generated code.
|
|
|
|
Per: https://github.com/NixOS/nixpkgs/issues/108938
|
|
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
|
|
|
|
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
|
|
https://github.com/gotify/server/releases/tag/v2.0.19
https://github.com/gotify/server/releases/tag/v2.0.20
|
|
Use new line in printf calls of update.sh, so editor config CI check
won't fail.
|
|
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
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Improved update script / procedure by getting all versions and shas
needed to build it.
|
|
This reverts commit 4e6bf03504c9e09f067cc6dee6b5aeec43a1405c, reversing
changes made to afd997aab6e9b7a322198092c7828d6c560ac06f.
Instead we propagate those frameworks from the compiler again
|
|
|
|
|
|
https://github.com/gotify/server/releases/tag/v2.0.13
|
|
|
|
|
|
|
