1
0
Fork 0
mirror of https://github.com/imtbl/hydrus-server-docker synced 2024-06-11 23:24:53 +12:00

Merge branch 'release/2.8.0'

This commit is contained in:
Michael Serajnik 2019-03-24 12:54:53 +01:00
commit 9477b4dce3
No known key found for this signature in database
GPG key ID: B390A5CBA3ECB74D
4 changed files with 30 additions and 9 deletions

View file

@ -7,6 +7,16 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
## [Unreleased] ## [Unreleased]
## [2.8.0] - 2019-03-24
### Added
+ Added default volume
### Changed
+ Updated hydrus server version
## [2.7.0] - 2019-03-14 ## [2.7.0] - 2019-03-14
### Changed ### Changed
@ -119,7 +129,8 @@ and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.
+ Initial release + Initial release
[Unreleased]: https://github.com/mserajnik/hydrus-server-docker/compare/2.7.0...develop [Unreleased]: https://github.com/mserajnik/hydrus-server-docker/compare/2.8.0...develop
[2.8.0]: https://github.com/mserajnik/hydrus-server-docker/compare/2.7.0...2.8.0
[2.7.0]: https://github.com/mserajnik/hydrus-server-docker/compare/2.6.0...2.7.0 [2.7.0]: https://github.com/mserajnik/hydrus-server-docker/compare/2.6.0...2.7.0
[2.6.0]: https://github.com/mserajnik/hydrus-server-docker/compare/2.5.0...2.6.0 [2.6.0]: https://github.com/mserajnik/hydrus-server-docker/compare/2.5.0...2.6.0
[2.5.0]: https://github.com/mserajnik/hydrus-server-docker/compare/2.4.0...2.5.0 [2.5.0]: https://github.com/mserajnik/hydrus-server-docker/compare/2.4.0...2.5.0

View file

@ -67,6 +67,8 @@ HEALTHCHECK --interval=1m --timeout=10s --retries=3 \
CMD wget --quiet --tries=1 --no-check-certificate --spider \ CMD wget --quiet --tries=1 --no-check-certificate --spider \
https://localhost:45870 || exit 1 https://localhost:45870 || exit 1
VOLUME /data
USER hydrus USER hydrus
ENTRYPOINT ["docker-entrypoint"] ENTRYPOINT ["docker-entrypoint"]

View file

@ -5,7 +5,7 @@
This is a simple Alpine-based Docker setup for running This is a simple Alpine-based Docker setup for running
[hydrus server][hydrus-server] from source. [hydrus server][hydrus-server] from source.
The latest build runs [hydrus server version 343][hydrus-server-version]. The latest build runs [hydrus server version 344][hydrus-server-version].
## Table of contents ## Table of contents
@ -33,7 +33,7 @@ By default, this will pull the latest build. To specify an image with a
specific version of hydrus server, provide the version number as tag, e.g.: specific version of hydrus server, provide the version number as tag, e.g.:
```zsh ```zsh
user@local:~$ docker pull mserajnik/hydrus-server-docker:343 user@local:~$ docker pull mserajnik/hydrus-server-docker:344
``` ```
See [here][docker-hub-tags] for all the available version numbers/tags. See [here][docker-hub-tags] for all the available version numbers/tags.
@ -95,9 +95,10 @@ repositories. You will generally have two (one for tags and one for files), but
if you add more, you will also need to expose additional ports. if you add more, you will also need to expose additional ports.
Per default, hydrus-server-docker stores its databases and media inside the Per default, hydrus-server-docker stores its databases and media inside the
`/data` directory. It is highly recommended to create a named volume and mount `/data` directory which is a mount point that is persisted as a volume. A new
it to the same location if you wish to persist the data beyond the lifetime of volume will be created every time a container is created, making it less ideal
the container and/or access it on the host: as a long-term solution. Instead, you should create a named volume yourself and
mount that over it instead:
```zsh ```zsh
user@local:~$ docker volume create hydrus-server-data user@local:~$ docker volume create hydrus-server-data
@ -110,6 +111,13 @@ example with all the options mentioned above:
user@local:~$ docker run -p 45870:45870 -p 45871:45871 -p 45872:45872 -v hydrus-server-data:/data -d mserajnik/hydrus-server-docker user@local:~$ docker run -p 45870:45870 -p 45871:45871 -p 45872:45872 -v hydrus-server-data:/data -d mserajnik/hydrus-server-docker
``` ```
Specifying the same named volume every time a container is created gives each
of these instances access to the same persisted data.
Of course, using a bind mount instead of a named volume is also possible but
for performance reasons only recommended if you need easy access to the data on
the host machine.
### Additional configuration when building ### Additional configuration when building
#### UID/GID #### UID/GID
@ -152,13 +160,13 @@ You are welcome to help out!
[MIT](LICENSE.md) © Michael Serajnik [MIT](LICENSE.md) © Michael Serajnik
[hydrus-server]: http://hydrusnetwork.github.io/hydrus/ [hydrus-server]: http://hydrusnetwork.github.io/hydrus/
[hydrus-server-version]: https://github.com/hydrusnetwork/hydrus/releases/tag/v343 [hydrus-server-version]: https://github.com/hydrusnetwork/hydrus/releases/tag/v344
[docker-hub]: https://hub.docker.com/r/mserajnik/hydrus-server-docker/ [docker-hub]: https://hub.docker.com/r/mserajnik/hydrus-server-docker/
[docker-hub-tags]: https://hub.docker.com/r/mserajnik/hydrus-server-docker/tags/ [docker-hub-tags]: https://hub.docker.com/r/mserajnik/hydrus-server-docker/tags/
[docker]: https://www.docker.com/ [docker]: https://www.docker.com/
[semantic-versioning]: https://semver.org/ [semantic-versioning]: https://semver.org/
[hydrus-server-badge]: https://img.shields.io/badge/hydrus%20server-version%20343-blue.svg [hydrus-server-badge]: https://img.shields.io/badge/hydrus%20server-version%20344-blue.svg
[travis]: https://travis-ci.com/mserajnik/hydrus-server-docker [travis]: https://travis-ci.com/mserajnik/hydrus-server-docker
[travis-badge]: https://travis-ci.com/mserajnik/hydrus-server-docker.svg [travis-badge]: https://travis-ci.com/mserajnik/hydrus-server-docker.svg

2
hydrus

@ -1 +1 @@
Subproject commit 67e39d8f88a080403b73cf1f6b5c423af7dc6243 Subproject commit f7763b38eea827b7494c8ea2ad54b96f1fcea818