kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Templated Files
LinuxServer-CI
rodzic
43b36f9328
commit
d3d0477cad
|
|
@ -1,6 +1,12 @@
|
||||||
# linuxserver/piwigo
|
# [linuxserver/piwigo](https://github.com/linuxserver/docker-piwigo)
|
||||||
|
|
||||||
[](https://discord.gg/YWrKVTn) [](https://microbadger.com/images/linuxserver/piwigo) [](https://microbadger.com/images/linuxserver/piwigo)   [](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-piwigo/job/master/) [](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/piwigo/latest/index.html)
|
[](https://discord.gg/YWrKVTn)
|
||||||
|
[](https://microbadger.com/images/linuxserver/piwigo "Get your own version badge on microbadger.com")
|
||||||
|
[](https://microbadger.com/images/linuxserver/piwigo "Get your own version badge on microbadger.com")
|
||||||
|
|
||||||
|
|
||||||
|
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-piwigo/job/master/)
|
||||||
|
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/piwigo/latest/index.html)
|
||||||
|
|
||||||
[Piwigo](http://piwigo.org/) is a photo gallery software for the web that comes with powerful features to publish and manage your collection of pictures.
|
[Piwigo](http://piwigo.org/) is a photo gallery software for the web that comes with powerful features to publish and manage your collection of pictures.
|
||||||
|
|
||||||
|
|
@ -13,18 +19,19 @@ Simply pulling `linuxserver/piwigo` should retrieve the correct image for your a
|
||||||
The architectures supported by this image are:
|
The architectures supported by this image are:
|
||||||
|
|
||||||
| Architecture | Tag |
|
| Architecture | Tag |
|
||||||
| :---: | :--- |
|
| :----: | --- |
|
||||||
| x86-64 | amd64-latest |
|
| x86-64 | amd64-latest |
|
||||||
| arm64 | arm64v8-latest |
|
| arm64 | arm64v8-latest |
|
||||||
| armhf | arm32v6-latest |
|
| armhf | arm32v6-latest |
|
||||||
|
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
|
||||||
Here are some example snippets to help you get started creating a container from this image.
|
Here are some example snippets to help you get started creating a container from this image.
|
||||||
|
|
||||||
### docker
|
### docker
|
||||||
|
|
||||||
```text
|
```
|
||||||
docker create \
|
docker create \
|
||||||
--name=piwigo \
|
--name=piwigo \
|
||||||
-e PUID=1000 \
|
-e PUID=1000 \
|
||||||
|
|
@ -36,6 +43,7 @@ docker create \
|
||||||
linuxserver/piwigo
|
linuxserver/piwigo
|
||||||
```
|
```
|
||||||
|
|
||||||
|
|
||||||
### docker-compose
|
### docker-compose
|
||||||
|
|
||||||
Compatible with docker-compose v2 schemas.
|
Compatible with docker-compose v2 schemas.
|
||||||
|
|
@ -60,37 +68,40 @@ services:
|
||||||
|
|
||||||
## Parameters
|
## Parameters
|
||||||
|
|
||||||
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.
|
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`\)
|
### Ports (`-p`)
|
||||||
|
|
||||||
| Parameter | Function |
|
| Parameter | Function |
|
||||||
| :---: | :--- |
|
| :----: | --- |
|
||||||
| `80` | Application WebUI |
|
| `80` | Application WebUI |
|
||||||
|
|
||||||
### Environment Variables \(`-e`\)
|
|
||||||
|
### Environment Variables (`-e`)
|
||||||
|
|
||||||
| Env | Function |
|
| Env | Function |
|
||||||
| :---: | :--- |
|
| :----: | --- |
|
||||||
| `PUID=1000` | for UserID - see below for explanation |
|
| `PUID=1000` | for UserID - see below for explanation |
|
||||||
| `PGID=1000` | for GroupID - see below for explanation |
|
| `PGID=1000` | for GroupID - see below for explanation |
|
||||||
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London. |
|
| `TZ=Europe/London` | Specify a timezone to use EG Europe/London. |
|
||||||
|
|
||||||
### Volume Mappings \(`-v`\)
|
### Volume Mappings (`-v`)
|
||||||
|
|
||||||
| Volume | Function |
|
| Volume | Function |
|
||||||
| :---: | :--- |
|
| :----: | --- |
|
||||||
| `/config` | Configuration files. |
|
| `/config` | Configuration files. |
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
## User / Group Identifiers
|
## User / Group Identifiers
|
||||||
|
|
||||||
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`.
|
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`.
|
||||||
|
|
||||||
Ensure any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
|
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=1000` and `PGID=1000`, to find yours use `id user` as below:
|
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
|
||||||
|
|
||||||
```text
|
```
|
||||||
$ id username
|
$ id username
|
||||||
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
||||||
```
|
```
|
||||||
|
|
@ -99,10 +110,11 @@ In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as bel
|
||||||
|
|
||||||
* You must create a user and database for piwigo to use in a mysql/mariadb server.
|
* You must create a user and database for piwigo to use in a mysql/mariadb server.
|
||||||
* In the setup page for database, use the ip address rather than hostname.
|
* In the setup page for database, use the ip address rather than hostname.
|
||||||
* A basic nginx configuration file can be found in `/config/nginx/site-confs`, edit the file to enable ssl \(port 443 by default\), set servername etc.
|
* A basic nginx configuration file can be found in `/config/nginx/site-confs`, edit the file to enable ssl (port 443 by default), set servername etc.
|
||||||
* Self-signed keys are generated the first time you run the container and can be found in `/config/keys`, if needed, you can replace them with your own.
|
* Self-signed keys are generated the first time you run the container and can be found in `/config/keys`, if needed, you can replace them with your own.
|
||||||
* The easiest way to edit the configuration file is to enable local files editor from the plugins page and use it to configure email settings etc.
|
* The easiest way to edit the configuration file is to enable local files editor from the plugins page and use it to configure email settings etc.
|
||||||
|
|
||||||
|
|
||||||
## Support Info
|
## Support Info
|
||||||
|
|
||||||
* Shell access whilst the container is running:
|
* Shell access whilst the container is running:
|
||||||
|
|
@ -127,4 +139,3 @@ In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as bel
|
||||||
* **14.10.16:** - Add version layer information.
|
* **14.10.16:** - Add version layer information.
|
||||||
* **10.09.16:** - Add layer badges to README.
|
* **10.09.16:** - Add layer badges to README.
|
||||||
* **29.08.15:** - Initial Release.
|
* **29.08.15:** - Initial Release.
|
||||||
|
|
||||||
|
|
|
||||||
Ładowanie…
Reference in New Issue