kopia lustrzana https://github.com/linuxserver/docker-documentation
Bot Updating Templated Files
LinuxServer-CI
rodzic
5b729ed5f2
commit
fa72b0fdd1
|
|
@ -0,0 +1,150 @@
|
|||
# [linuxserver/pydio](https://github.com/linuxserver/docker-pydio)
|
||||
|
||||
[](https://discord.gg/YWrKVTn)
|
||||
[](https://microbadger.com/images/linuxserver/pydio "Get your own version badge on microbadger.com")
|
||||
[](https://microbadger.com/images/linuxserver/pydio "Get your own version badge on microbadger.com")
|
||||
|
||||
|
||||
[](https://ci.linuxserver.io/job/Docker-Pipeline-Builders/job/docker-pydio/job/master/)
|
||||
[](https://lsio-ci.ams3.digitaloceanspaces.com/linuxserver/pydio/latest/index.html)
|
||||
|
||||
[Pydio](https://pydio.com/) (formerly AjaXplorer) is a mature open source software solution for file sharing and synchronization. With intuitive user interfaces (web / mobile / desktop), Pydio provides enterprise-grade features to gain back control and privacy of your data: user directory connectors, legacy filesystems drivers, comprehensive admin interface, and much more.
|
||||
|
||||
## 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).
|
||||
|
||||
Simply pulling `linuxserver/pydio` 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 |
|
||||
|
||||
|
||||
## Usage
|
||||
|
||||
Here are some example snippets to help you get started creating a container from this image.
|
||||
|
||||
### docker
|
||||
|
||||
```
|
||||
docker create \
|
||||
--name=pydio \
|
||||
-e PUID=1001 \
|
||||
-e PGID=1001 \
|
||||
-e TZ=Europe/London \
|
||||
-p 443:443 \
|
||||
-v <path to data>:/config \
|
||||
-v <path to data>:/data \
|
||||
--restart unless-stopped \
|
||||
linuxserver/pydio
|
||||
```
|
||||
|
||||
|
||||
### docker-compose
|
||||
|
||||
Compatible with docker-compose v2 schemas.
|
||||
|
||||
```yaml
|
||||
---
|
||||
version: "2"
|
||||
services:
|
||||
pydio:
|
||||
image: linuxserver/pydio
|
||||
container_name: pydio
|
||||
environment:
|
||||
- PUID=1001
|
||||
- PGID=1001
|
||||
- TZ=Europe/London
|
||||
volumes:
|
||||
- <path to data>:/config
|
||||
- <path to data>:/data
|
||||
ports:
|
||||
- 443:443
|
||||
mem_limit: 4096m
|
||||
restart: unless-stopped
|
||||
```
|
||||
|
||||
## 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 |
|
||||
| :----: | --- |
|
||||
| `443` | WebUI |
|
||||
|
||||
|
||||
### 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. |
|
||||
|
||||
### Volume Mappings (`-v`)
|
||||
|
||||
| Volume | Function |
|
||||
| :----: | --- |
|
||||
| `/config` | Where pydio should store it's configuration files. |
|
||||
| `/data` | Where pydio should store uploaded files. |
|
||||
|
||||
|
||||
|
||||
## 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=1001` and `PGID=1001`, to find yours use `id user` as below:
|
||||
|
||||
```
|
||||
$ id username
|
||||
uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)
|
||||
```
|
||||
|
||||
## Application Setup
|
||||
|
||||
You must create a user and database for pydio to use in a mysql/mariadb or postgresql server. You can use sqlite with no further config needed, but this should only be considered for testing purposes.
|
||||
In the setup page for database, use the ip address rather than hostname...
|
||||
|
||||
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.
|
||||
|
||||
For public link sharing to function correctly be sure to change the Detected Server Url to the URL of your pydio instance in the setup wizard.
|
||||
|
||||
For email settings edit the file /config/ssmtp.conf and restart the container.
|
||||
|
||||
|
||||
|
||||
## Support Info
|
||||
|
||||
* Shell access whilst the container is running:
|
||||
* `docker exec -it pydio /bin/bash`
|
||||
* To monitor the logs of the container in realtime:
|
||||
* `docker logs -f pydio`
|
||||
* Container version number
|
||||
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' pydio`
|
||||
* Image version number
|
||||
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/pydio`
|
||||
|
||||
## Versions
|
||||
|
||||
* **11.02.19:** - Add pipeline logic and multi arch, rebase to alpine 3.8.
|
||||
* **12.01.18:** - Rebase to alpine linux 3.7.
|
||||
* **28.10.17:** - php7-ssh2 moved from testing to community repo.
|
||||
* **25.05.17:** - Rebase to alpine linux 3.6.
|
||||
* **17.05.17:** - Make default install pydio 8.
|
||||
* **03.05.17:** - Use repo pinning to better solve dependencies, use repo version of php7-imagick.
|
||||
* **28.02.17:** - Modify sed for data path.
|
||||
* **18.02.17:** - Rebase to alpine linux 3.5.
|
||||
* **05.11.16:** - Pinned at latest sourceforge download version, in lieu of a full rewrite.
|
||||
* **14.10.16:** - Add version layer information.
|
||||
* **10.09.16:** - Add layer badges to README.
|
||||
* **08.09.15:** - Initial Release.
|
||||
Ładowanie…
Reference in New Issue