2024-09-06 20:49:02 by Benny Siegert | Files touched by this commit (180) | |
Log message:
Revbump all Go packages after go122 update
|
2024-08-11 17:57:15 by Benny Siegert | Files touched by this commit (176) | |
Log message:
Revbump all Go packages after update
|
2024-08-06 14:54:42 by Thomas Klausner | Files touched by this commit (3) | |
Log message:
restic-rest-server: update to 0.13.0.
Changelog for rest-server 0.13.0 (2024-07-26)
============================================
The following sections list the changes in rest-server 0.13.0 relevant
to users. The changes are ordered by importance.
Summary
-------
* Chg #267: Update dependencies and require Go 1.18 or newer
* Chg #273: Shut down cleanly on TERM and INT signals
* Enh #271: Print listening address after start-up
* Enh #272: Support listening on a unix socket
Details
-------
* Change #267: Update dependencies and require Go 1.18 or newer
Most dependencies have been updated. Since some libraries require newer language
features, support for Go 1.17 has been dropped, which means that rest-server now
requires at least Go 1.18 to build.
https://github.com/restic/rest-server/pull/267
* Change #273: Shut down cleanly on TERM and INT signals
Rest-server now listens for TERM and INT signals and cleanly closes down the
http.Server and listener when receiving either of them.
This is particularly useful when listening on a unix socket, as the server will
now remove the socket file when it shuts down.
https://github.com/restic/rest-server/pull/273
* Enhancement #271: Print listening address after start-up
When started with `--listen :0`, rest-server would print `start server on :0`
The message now also includes the actual address listened on, for example `start
server on 0.0.0.0:37333`. This is useful when starting a server with an
auto-allocated free port number (port 0).
https://github.com/restic/rest-server/pull/271
* Enhancement #272: Support listening on a unix socket
It is now possible to make rest-server listen on a unix socket by prefixing the
socket filename with `unix:` and passing it to the `--listen` option, for
example `--listen unix:/tmp/foo`.
This is useful in combination with remote port forwarding to enable a remote
server to backup locally, e.g.:
```
rest-server --listen unix:/tmp/foo &
ssh -R /tmp/foo:/tmp/foo user@host restic -r rest:http+unix:///tmp/foo:/repo \
backup
```
https://github.com/restic/rest-server/pull/272
Changelog for rest-server 0.12.1 (2023-07-09)
============================================
The following sections list the changes in rest-server 0.12.1 relevant
to users. The changes are ordered by importance.
Summary
-------
* Fix #230: Fix erroneous warnings about unsupported fsync
* Fix #238: API: Return empty array when listing empty folders
* Enh #217: Log to stdout using the `--log -` option
Details
-------
* Bugfix #230: Fix erroneous warnings about unsupported fsync
Due to a regression in rest-server 0.12.0, it continuously printed `WARNING:
fsync is not supported by the data storage. This can lead to data loss, if the
system crashes or the storage is unexpectedly disconnected.` for systems that
support fsync. We have fixed the warning.
https://github.com/restic/rest-server/issues/230
https://github.com/restic/rest-server/pull/231
* Bugfix #238: API: Return empty array when listing empty folders
Rest-server returned `null` when listing an empty folder. This has been changed
to returning an empty array in accordance with the REST protocol specification.
This change has no impact on restic users.
https://github.com/restic/rest-server/issues/238
https://github.com/restic/rest-server/pull/239
* Enhancement #217: Log to stdout using the `--log -` option
Logging to stdout was possible using `--log /dev/stdout`. However, when the rest
server is run as a different user, for example, using
`sudo -u restic rest-server [...] --log /dev/stdout`
This did not work due to permission issues.
For logging to stdout, the `--log` option now supports the special filename `-`
which also works in these cases.
https://github.com/restic/rest-server/pull/217
|
2024-07-03 08:59:36 by Benny Siegert | Files touched by this commit (169) | |
Log message:
Revbump all Go packages after go122 security update
|
2024-06-13 15:47:13 by Benny Siegert | Files touched by this commit (169) | |
Log message:
Revbump all Go packages after go122 update
|
2024-06-01 16:03:06 by Benny Siegert | Files touched by this commit (168) |
Log message:
Revbump all Go packages, default Go version is now 1.22.
|
2024-04-05 21:14:14 by Benny Siegert | Files touched by this commit (161) | |
Log message:
Revbump all Go packages after go121 update
|
2024-02-07 15:51:04 by Benny Siegert | Files touched by this commit (156) | |
Log message:
Revbump all Go packages after go121 update
|
2024-01-10 20:14:43 by Benny Siegert | Files touched by this commit (152) | |
Log message:
Revbump all Go packages after go121 update
|
2023-12-05 20:46:19 by Benny Siegert | Files touched by this commit (146) | |
Log message:
Revbump all Go packages after go121 update
|