Bot Updating Templated Files

pull/1/head
LinuxServer-CI 2019-02-12 14:39:12 +00:00
rodzic efb5ffa8ee
commit aa8f94503e
1 zmienionych plików z 119 dodań i 64 usunięć

Wyświetl plik

@ -1,81 +1,128 @@
[linuxserverurl]: https://linuxserver.io
[forumurl]: https://forum.linuxserver.io
[ircurl]: https://www.linuxserver.io/irc/
[podcasturl]: https://www.linuxserver.io/podcast/
[appurl]: https://vaemendis.net/ubooquity/
[hub]: https://hub.docker.com/r/linuxserver/ubooquity/
# [linuxserver/ubooquity](https://github.com/linuxserver/docker-ubooquity)
[![linuxserver.io](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/linuxserver_medium.png)][linuxserverurl]
[![](https://img.shields.io/discord/354974912613449730.svg?logo=discord&label=LSIO%20Discord&style=flat-square)](https://discord.gg/YWrKVTn)
[![](https://images.microbadger.com/badges/version/linuxserver/ubooquity.svg)](https://microbadger.com/images/linuxserver/ubooquity "Get your own version badge on microbadger.com")
[![](https://images.microbadger.com/badges/image/linuxserver/ubooquity.svg)](https://microbadger.com/images/linuxserver/ubooquity "Get your own version badge on microbadger.com")
![Docker Pulls](https://img.shields.io/docker/pulls/linuxserver/ubooquity.svg)
![Docker Stars](https://img.shields.io/docker/stars/linuxserver/ubooquity.svg)
[![Build Status](https://ci.linuxserver.io/buildStatus/icon?job=Docker-Pipeline-Builders/docker-ubooquity/master)](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-ubooquity/job/master/)
[![](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/ubooquity/latest/badge.svg)](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/ubooquity/latest/index.html)
The [LinuxServer.io][linuxserverurl] team brings you another container release featuring easy user mapping and community support. Find us for support at:
* [forum.linuxserver.io][forumurl]
* [IRC][ircurl] on freenode at `#linuxserver.io`
* [Podcast][podcasturl] covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!
[Ubooquity](https://vaemendis.net/ubooquity/) is a free, lightweight and easy-to-use home server for your comics and ebooks. Use it to access your files from anywhere, with a tablet, an e-reader, a phone or a computer.
# linuxserver/ubooquity
[![](https://images.microbadger.com/badges/version/linuxserver/ubooquity.svg)](https://microbadger.com/images/linuxserver/ubooquity "Get your own version badge on microbadger.com")[![](https://images.microbadger.com/badges/image/linuxserver/ubooquity.svg)](https://microbadger.com/images/linuxserver/ubooquity "Get your own image badge on microbadger.com")[![Docker Pulls](https://img.shields.io/docker/pulls/linuxserver/ubooquity.svg)][hub][![Docker Stars](https://img.shields.io/docker/stars/linuxserver/ubooquity.svg)][hub][![Build Status](https://ci.linuxserver.io/buildStatus/icon?job=Docker-Builders/x86-64/x86-64-ubooquity)](https://ci.linuxserver.io/job/Docker-Builders/job/x86-64/job/x86-64-ubooquity/)
## Supported Architectures
Ubooquity is a free, lightweight and easy-to-use home server for your comics and ebooks. Use it to access your files from anywhere, with a tablet, an e-reader, a phone or a computer.
Our images support multiple architectures such as `x86-64`, `arm64` and `armhf`. We utilise the docker manifest for multi-platform awareness. More information is available from docker [here](https://github.com/docker/distribution/blob/master/docs/spec/manifest-v2-2.md#manifest-list).
Simply pulling `linuxserver/ubooquity` should retrieve the correct image for your arch, but you can also pull specific arch images via tags.
The architectures supported by this image are:
| Architecture | Tag |
| :----: | --- |
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v6-latest |
[![ubooquity](https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/ubooquity-banner.png)][appurl]
## Usage
Here are some example snippets to help you get started creating a container from this image.
### docker
```
docker create \
--name=ubooquity \
-e PUID=1001 \
-e PGID=1001 \
-e TZ=Europe/London \
-e MAXMEM=<maxmem> \
-p 2202:2202 \
-p 2203:2203 \
-v <path to data>:/config \
-v <path to books>:/books \
-v <path to comics>:/comics \
-v <path to raw files>:/files \
-e MAXMEM=<maxmem> \
-e PGID=<gid> -e PUID=<uid> \
-p 2202:2202 \
-p 2203:2203 \
--restart unless-stopped \
linuxserver/ubooquity
```
### docker-compose
Compatible with docker-compose v2 schemas.
```yaml
---
version: "2"
services:
ubooquity:
image: linuxserver/ubooquity
container_name: ubooquity
environment:
- PUID=1001
- PGID=1001
- TZ=Europe/London
- MAXMEM=<maxmem>
volumes:
- <path to data>:/config
- <path to books>:/books
- <path to comics>:/comics
- <path to raw files>:/files
ports:
- 2202:2202
- 2203:2203
mem_limit: 4096m
restart: unless-stopped
```
## Parameters
`The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side.
For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container.
So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080
http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.`
Docker images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `<external>:<internal>` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
### Ports (`-p`)
| Parameter | Function |
| :----: | --- |
| `2202` | The library port. |
| `2203` | The admin port. |
### Environment Variables (`-e`)
| Env | Function |
| :----: | --- |
| `PUID=1001` | for UserID - see below for explanation |
| `PGID=1001` | for GroupID - see below for explanation |
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London. |
| `MAXMEM=<maxmem>` | To set the maximum memory. |
### Volume Mappings (`-v`)
| Volume | Function |
| :----: | --- |
| `/config` | Config files and database for ubooquity. |
| `/books` | Location of books. |
| `/comics` | Location of comics. |
| `/files` | Location of raw files. |
* `-p 2202` - the library port
* `-p 2203` - the admin port
* `-v /config` - Config files and database for ubooquity
* `-v /books` - Location of books.
* `-v /comics` - Location of comics.
* `-v /files` - Location of raw files.
* `-e MAXMEM` - to set the maximum memory
* `-e PGID` for GroupID - see below for explanation
* `-e PUID` for UserID - see below for explanation
## User / Group Identifiers
It is based on alpine linux with s6 overlay, for shell access whilst the container is running do `docker exec -it ubooquity /bin/bash`.
When using volumes (`-v` flags), permissions issues can arise between the host OS and the container, we avoid this issue by allowing you to specify the user `PUID` and group `PGID`.
### MAXMEM
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
The quantity of memory allocated to Ubooquity depends on the hardware your are running it on. If this quantity is too small, you might sometime saturate it with when performing memory intensive operations. Thats when you get `java.lang.OutOfMemoryError:` Java heap space errors.
You can explicitly set the amount of memory Ubooquity is allowed to use (be careful to set a value lower than the actual physical memory of your hardware).
If no value is set it will default to 512MB.
### User / Group Identifiers
Sometimes when using data volumes (`-v` flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user `PUID` and group `PGID`. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" ™.
In this instance `PUID=1001` and `PGID=1001`. To find yours use `id user` as below:
In this instance `PUID=1001` and `PGID=1001`, to find yours use `id user` as below:
```
$ id <dockeruser>
$ id username
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
```
## Setting up the application
## Application Setup
**IMPORTANT**
Ubooquity has now been upgraded to [version 2](http://vaemendis.net/ubooquity/article19/ubooquity-2-1-0) and for existing v1.x users we recommend cleaning your appdata and reinstalling, due to changes in the application itself making the two versions essentially incompatible with each other. Also the admin page and library pages are now on separate ports as detailed below.
@ -86,28 +133,36 @@ Then you can access the webui at `http://<your-ip>:2202/ubooquity/`
This container will automatically scan your files at startup.
## Info
### MAXMEM
* Shell access whilst the container is running: `docker exec -it ubooquity /bin/bash`
* To monitor the logs of the container in realtime: `docker logs -f ubooquity`
The quantity of memory allocated to Ubooquity depends on the hardware your are running it on. If this quantity is too small, you might sometime saturate it with when performing memory intensive operations. Thats when you get `java.lang.OutOfMemoryError:` Java heap space errors.
* container version number
You can explicitly set the amount of memory Ubooquity is allowed to use (be careful to set a value lower than the actual physical memory of your hardware).
`docker inspect -f '{{ index .Config.Labels "build_version" }}' ubooquity`
If no value is set it will default to 512MB.
* image version number
`docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/ubooquity`
## Support Info
* Shell access whilst the container is running:
* `docker exec -it ubooquity /bin/bash`
* To monitor the logs of the container in realtime:
* `docker logs -f ubooquity`
* Container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ubooquity`
* Image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/ubooquity`
## Versions
+ **28.01.19:** Add pipeline logic and multi arch.
+ **15.10.18:** Upgrade to Ubooquity 2.1.2.
+ **23.08.18:** Rebase to alpine 3.8.
+ **09.12.17:** Rebase to alpine 3.7.
+ **07.10.17:** Upgrade to Ubooquity 2.1.1.
+ **16.07.17:** Upgrade to Ubooquity 2.1.0, see setting up application section for important info for existing v1.x users.
+ **26.05.17:** Rebase to alpine 3.6.
+ **08.04.17:** Switch to java from 3.5 repo, fixes login crashes.
+ **06.02.17:** Rebase to alpine 3.5.
+ **06.12.16:** Initial Release.
* **28.01.19:** - Add pipeline logic and multi arch.
* **15.10.18:** - Upgrade to Ubooquity 2.1.2.
* **23.08.18:** - Rebase to alpine 3.8.
* **09.12.17:** - Rebase to alpine 3.7.
* **07.10.17:** - Upgrade to Ubooquity 2.1.1.
* **16.07.17:** - Upgrade to Ubooquity 2.1.0, see setting up application section for important info for existing v1.x users.
* **26.05.17:** - Rebase to alpine 3.6.
* **08.04.17:** - Switch to java from 3.5 repo, fixes login crashes.
* **06.02.17:** - Rebase to alpine 3.5.
* **06.12.16:** - Initial Release.