Search Criteria
Package Details: mercure 0.16.3-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/mercure.git (read-only, click to copy) |
|---|---|
| Package Base: | mercure |
| Description: | Server-sent live updates: protocol and reference implementation |
| Upstream URL: | https://mercure.rocks |
| Licenses: | AGPL3 |
| Submitter: | Deuchnord |
| Maintainer: | Durag |
| Last Packager: | Durag |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2019-10-04 12:48 (UTC) |
| Last Updated: | 2024-09-12 03:57 (UTC) |
Latest Comments
kapiwko commented on 2024-09-11 11:16 (UTC)
0.16.2 The Caddyfile.dev file has been renamed dev.Caddyfile to match new Caddy best practices and prevent "ambigous adapter" issues.
0.14.4 This release is built on top of Caddy 2.6. Caddy 2.6 removed support for single-hyphen long-form flags (such as -config), use the double-hyphen syntax instead (--config).
0.14.1 The default dev key changed from !ChangeMe! to !ChangeThisMercureHubJWTSecretKey! to respect the specification (they key must longer than 256 bits).
Durag commented on 2021-04-11 17:12 (UTC)
@Dechnord Where you able to test the patch I've sent you? Where the permissions working for you as expected?
Deuchnord commented on 2021-03-06 09:54 (UTC)
@Durag thanks for your help in fixing this package!
Have you found a solution for the permissions issue when running though systemd? I couldn't find one on my side, and it looks like it's the last issue before I can publish the fixed package
Durag commented on 2021-03-03 11:20 (UTC) (edited on 2021-03-03 14:45 (UTC) by Durag)
Thanks againg for your fast response.
You need to update the sha256sums for the mercure.service file, otherwise the build fails.
Also the ExecReload parameter needs to be set to:
ExecReload=/usr/bin/mercure reload
With the current version its not possible for me to start the Mercure service with the systemd service. Manual start with my user works. It seems that the underlying Caddy server is missing permissions to write files.
The current version does not support configuration via /etc/mercure/mercure.yaml (this was only for the legacy version; https://mercure.rocks/docs/hub/config). Instead it can be configured via environment variables or a Caddyfile.
For this reason I would propose to create a minimal /etc/mercure/Caddyfile (see the minimal configuration on the mentioned link; be careful, it needs some tweaking because of permissions - I'm trying to figure it out myself) and update the ExecStart parameter of the systemd unit to:
ExecStart=/usr/bin/mercure start -config /etc/mercure/Caddyfile
This way, users don't need to edit the systemd unit file if they want to use a custom configuration.
Deuchnord commented on 2021-03-03 08:22 (UTC)
Thanks for the report, I didn't see the synopsis of the binary had changed. For the information, the lack of 32bits version is an upstream issue. I have informed the maintainer of Mercure, who is investigating it.
Durag commented on 2021-03-03 02:14 (UTC)
There is a bug in the systemd unit file.
The ExecStart parameter needs to be corrected to:
ExecStart=/usr/bin/mercure start
Durag commented on 2021-03-01 20:04 (UTC)
Oops... I haven't reloaded the page before editing my comment. The build of the new version works like a charm. Thank your for your really fast update!
Now I'll try to get it to work!
Deuchnord commented on 2021-03-01 16:59 (UTC)
Thanks @Durag, it should fixed now :)
Durag commented on 2021-03-01 16:10 (UTC) (edited on 2021-03-01 20:02 (UTC) by Durag)
The package process exits with the following error message:
==> Starting package()... install: cannot stat '/home/durag/.cache/yay/mercure/src/mercure/mercure': No such file or directory ==> ERROR: A failure occurred in package(). Aborting...
The build process and installation of the previous version works. I can start mercure manually, but I cannot get the systemd service to work.
A post installation message with some information would be nice.