kopia lustrzana https://github.com/linuxserver/docker-documentation
173 wiersze
8.9 KiB
Markdown
173 wiersze
8.9 KiB
Markdown
# [linuxserver/piwigo](https://github.com/linuxserver/docker-piwigo)
|
|
|
|
[](https://github.com/linuxserver/docker-piwigo)
|
|
[](https://github.com/linuxserver/docker-piwigo/releases)
|
|
[](https://github.com/linuxserver/docker-piwigo/packages)
|
|
[](https://gitlab.com/linuxserver.io/docker-piwigo/container_registry)
|
|
[](https://microbadger.com/images/linuxserver/piwigo "Get your own version badge on microbadger.com")
|
|
[](https://hub.docker.com/r/linuxserver/piwigo)
|
|
[](https://hub.docker.com/r/linuxserver/piwigo)
|
|
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-piwigo/job/master/)
|
|
[](https://ci-tests.linuxserver.io/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.
|
|
|
|
## Supported Architectures
|
|
|
|
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) and our announcement [here](https://blog.linuxserver.io/2019/02/21/the-lsio-pipeline-project/).
|
|
|
|
Simply pulling `ghcr.io/linuxserver/piwigo` 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 | arm32v7-latest |
|
|
|
|
|
|
## Usage
|
|
|
|
Here are some example snippets to help you get started creating a container from this image.
|
|
|
|
### docker-compose ([recommended](https://docs.linuxserver.io/general/docker-compose))
|
|
|
|
Compatible with docker-compose v2 schemas.
|
|
|
|
```yaml
|
|
---
|
|
version: "2.1"
|
|
services:
|
|
piwigo:
|
|
image: ghcr.io/linuxserver/piwigo
|
|
container_name: piwigo
|
|
environment:
|
|
- PUID=1000
|
|
- PGID=1000
|
|
- TZ=Europe/London
|
|
volumes:
|
|
- </path/to/appdata/config>:/config
|
|
ports:
|
|
- 80:80
|
|
restart: unless-stopped
|
|
```
|
|
|
|
### docker cli
|
|
|
|
```
|
|
docker run -d \
|
|
--name=piwigo \
|
|
-e PUID=1000 \
|
|
-e PGID=1000 \
|
|
-e TZ=Europe/London \
|
|
-p 80:80 \
|
|
-v </path/to/appdata/config>:/config \
|
|
--restart unless-stopped \
|
|
ghcr.io/linuxserver/piwigo
|
|
```
|
|
|
|
|
|
## 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.
|
|
|
|
### Ports (`-p`)
|
|
|
|
| Parameter | Function |
|
|
| :----: | --- |
|
|
| `80` | Application WebUI |
|
|
|
|
|
|
### Environment Variables (`-e`)
|
|
|
|
| Env | Function |
|
|
| :----: | --- |
|
|
| `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. |
|
|
|
|
### Volume Mappings (`-v`)
|
|
|
|
| Volume | Function |
|
|
| :----: | --- |
|
|
| `/config` | Configuration files. |
|
|
|
|
|
|
|
|
## Environment variables from files (Docker secrets)
|
|
|
|
You can set any environment variable from a file by using a special prepend `FILE__`.
|
|
|
|
As an example:
|
|
|
|
```
|
|
-e FILE__PASSWORD=/run/secrets/mysecretpassword
|
|
```
|
|
|
|
Will set the environment variable `PASSWORD` based on the contents of the `/run/secrets/mysecretpassword` file.
|
|
|
|
## Umask for running applications
|
|
|
|
For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional `-e UMASK=022` setting.
|
|
Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up [here](https://en.wikipedia.org/wiki/Umask) before asking for support.
|
|
|
|
|
|
## 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`.
|
|
|
|
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:
|
|
|
|
```
|
|
$ id username
|
|
uid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
|
|
```
|
|
|
|
## Application Setup
|
|
|
|
* 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.
|
|
* 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.
|
|
* 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.
|
|
|
|
## Docker Mods
|
|
[](https://mods.linuxserver.io/?mod=piwigo "view available mods for this container.") [](https://mods.linuxserver.io/?mod=universal "view available universal mods.")
|
|
|
|
We publish various [Docker Mods](https://github.com/linuxserver/docker-mods) to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.
|
|
|
|
|
|
## Support Info
|
|
|
|
* Shell access whilst the container is running:
|
|
* `docker exec -it piwigo /bin/bash`
|
|
* To monitor the logs of the container in realtime:
|
|
* `docker logs -f piwigo`
|
|
* Container version number
|
|
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' piwigo`
|
|
* Image version number
|
|
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' ghcr.io/linuxserver/piwigo`
|
|
|
|
## Versions
|
|
|
|
* **12.12.20:** - Increased upload_max_filesize in php.ini
|
|
* **01.06.20:** - Rebasing to alpine 3.12.
|
|
* **19.12.19:** - Rebasing to alpine 3.11.
|
|
* **28.06.19:** - Rebasing to alpine 3.10.
|
|
* **12.06.19:** - Add ffmpeg and other deps as needed by popular plugins.
|
|
* **23.03.19:** - Switching to new Base images, shift to arm32v7 tag.
|
|
* **01.03.19:** - Add php-ctype & php-curl.
|
|
* **22.02.19:** - Rebasing to alpine 3.9, add php-ldap.
|
|
* **28.01.19:** - Rebase to alpine linux 3.8 , add pipeline logic and multi arch.
|
|
* **25.01.18:** - Rebase to alpine linux 3.7.
|
|
* **25.05.17:** - Rebase to alpine linux 3.6.
|
|
* **03.05.17:** - Use repo pinning to better solve dependencies, use repo version of php7-imagick.
|
|
* **20.04.17:** - Add php7-exif package, thanks iiska
|
|
* **23.02.17:** - Rebase to alpine linux 3.5 and nginx.
|
|
* **14.10.16:** - Add version layer information.
|
|
* **10.09.16:** - Add layer badges to README.
|
|
* **29.08.15:** - Initial Release.
|