Bot Updating Templated Files

LICENSE
LinuxServer-CI 2019-03-04 08:20:50 +00:00
rodzic 98ebd62773
commit 6418575631
1 zmienionych plików z 10 dodań i 10 usunięć

Wyświetl plik

@ -34,8 +34,8 @@ Here are some example snippets to help you get started creating a container from
```
docker create \
--name=musicbrainz \
-e PUID=1001 \
-e PGID=1001 \
-e PUID=1000 \
-e PGID=1000 \
-e TZ=Europe/London \
-e BRAINZCODE=<code from musicbrainz> \
-e WEBADDRESS=<ip of host> \
@ -60,8 +60,8 @@ services:
image: linuxserver/musicbrainz
container_name: musicbrainz
environment:
- PUID=1001
- PGID=1001
- PUID=1000
- PGID=1000
- TZ=Europe/London
- BRAINZCODE=<code from musicbrainz>
- WEBADDRESS=<ip of host>
@ -71,7 +71,6 @@ services:
- </path/to/appdata/config>:/data
ports:
- 5000:5000
mem_limit: 4096m
restart: unless-stopped
```
@ -90,8 +89,8 @@ Docker images are configured using parameters passed at runtime (such as those a
| Env | Function |
| :----: | --- |
| `PUID=1001` | for UserID - see below for explanation |
| `PGID=1001` | for GroupID - see below for explanation |
| `PUID=1000` | for UserID - see below for explanation |
| `PGID=1000` | for GroupID - see below for explanation |
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London |
| `BRAINZCODE=<code from musicbrainz>` | To enter musicbrainz code. see Setting up the application |
| `WEBADDRESS=<ip of host>` | To set ip for host to allow css to render properly, DO NOT ENTER PORT NUMBER. |
@ -112,16 +111,16 @@ When using volumes (`-v` flags), permissions issues can arise between the host O
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance `PUID=1001` and `PGID=1001`, to find yours use `id user` as below:
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
```
$ id username
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
```
## Application Setup
+ For schema 24 updates you should pull the latest image, clear all files and folders in /config and /data and reinitiate the database import by (re)starting the docker.
+ For all updates you should pull the latest image, clear all files and folders in /config and /data and reinitiate the database import by (re)starting the docker. We do not officially support upgrading this container in place with existing data sets.
+ **If you did not set WEBADDRESS env variable, then AFTER iniatilisation is complete you will need to edit the line `sub WEB_SERVER { "localhost:5000" }` in file /config/DBDefs.pm changing localhost to the ip of your host, this is to allow css to display properly**
@ -144,6 +143,7 @@ In this instance `PUID=1001` and `PGID=1001`, to find yours use `id user` as bel
## Versions
* **02.03.19:** - Revert to alpine 3.8 to fix incompatibilities with frontend build tools.
* **19.02.19:** - Multi Arch and add pipeline logic, rebase to Alpine 3.9
* **22.08.18:** - Bump server version 2018-08-14.
* **30.06.18:** - Bump server version 2018-06-30.