Package Details: gotify-server 2.1.4-1

Git Clone URL: https://aur.archlinux.org/gotify-server.git (read-only, click to copy)
Package Base: gotify-server
Description: A simple server for sending and receiving messages in real-time per WebSocket.
Upstream URL: https://gotify.net/
Keywords: gotify notification push real server time websocket
Licenses: MIT
Submitter: matthias.lisin
Maintainer: jmattheis (matthias.lisin)
Last Packager: jmattheis
Votes: 4
Popularity: 0.006842
First Submitted: 2020-01-19 19:42
Last Updated: 2022-01-12 18:34

Latest Comments

1 2 Next › Last »

jmattheis commented on 2021-12-04 21:45

@Xyne the build of this package should work now. The release binaries for the new gotify/server version will follow soon, there was an error on the build pipeline.

Xyne commented on 2021-12-04 21:31

@jmattheis Thanks for the reply. After posting I discovered that nodejs 17.x was the culprit so I tested it with 17.2 which hasn't been packaged yet. I get the same errors. From what I can tell, this bug affects several projects so hopefully it will get fixed soon.

I'll use the gotify-server-bin package until the bug is fixed. I've just updated that package, which now includes the service file from this one because it has more hardening options.

I've subscribed to notifications here. Please post a message once the package is working again.

Thanks for maintaining this!

jmattheis commented on 2021-12-04 19:11

@Xyne the UI will be embedded into the binary with a virtual file system, hence the absolute path /ui. The UI is build via yarn build and embedded via go run hack/packr/packr.go -- .. It seems the building of the UI broke with node 17.x this must be fixed upstream. I've created https://github.com/gotify/server/issues/455 for this.

Xyne commented on 2021-12-04 14:57

When trying to start the service, I get the following error:

gotify-server.service: Main process exited, code=exited, status=2/INVALIDARGUMENT

The error in /var/logs/gotify/server.log is

Starting Gotify version 2.1.0@2021-12-04-01:34:48
panic: stat /ui/build/index.html: no such file or directory

Is the package supposed to include static HTML files? If so, where are they supposed to be installed? Surely not under /ui/?

sudobash418 commented on 2020-07-29 03:09

Ah, I checked my config file and it was configured to use /var/lib/gotify-server instead of /var/lib/gotify; with /var/lib/gotify it works perfectly fine without my systemd override.

Guess that'll teach me to check my configs before anything else, thanks for the tip.

matthias.lisin commented on 2020-07-28 15:31

@sudobash418 Hey, thanks for reporting, I'll check asap. Do you use any custom settings or systemd overrides?

sudobash418 commented on 2020-07-24 04:18

Not sure if this is just a problem with my setup, but with 2.0.17 I kept getting this error: "Internal Server Error: attempted to write to readonly database"

I eventually solved it by adding the following to the systemd service via systemctl edit gotify-server.service:

[Service]
ReadWritePaths=/var/lib/gotify-server

loserMcloser commented on 2020-07-18 22:22

@jmattheis Thanks!

A note for others: I had more difficulties compiling with gcc-go, but plain go worked.

jmattheis commented on 2020-07-18 20:47

@loserMcloser This should be fixed in the latest version.

loserMcloser commented on 2020-07-18 05:06

go: github.com/Southclaws/configor@v1.0.0: reading github.com/Southclaws/configor/go.mod at revision v1.0.0: unknown revision v1.0.0 ==> ERROR: A failure occurred in build(). Aborting...