[](https://microbadger.com/images/linuxserver/projectsend "Get your own version badge on microbadger.com")
[](https://microbadger.com/images/linuxserver/projectsend "Get your own version badge on microbadger.com")
[Projectsend](http://www.projectsend.org) is a self-hosted application that lets you upload files and assign them to specific clients that you create yourself. Secure, private and easy. No more depending on external services or e-mail to send those files.
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 `linuxserver/projectsend` 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=projectsend \
-e PUID=1001 \
-e PGID=1001 \
-e TZ=Europe/London \
-e MAX_UPLOAD=<5000> \
-p 80:80 \
-v <pathtodata>:/config \
-v <pathtodata>:/data \
--restart unless-stopped \
linuxserver/projectsend
```
### docker-compose
Compatible with docker-compose v2 schemas.
```yaml
---
version: "2"
services:
projectsend:
image: linuxserver/projectsend
container_name: projectsend
environment:
- PUID=1001
- PGID=1001
- TZ=Europe/London
- MAX_UPLOAD=<5000>
volumes:
-<pathtodata>:/config
-<pathtodata>:/data
ports:
- 80:80
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 |
| :----: | --- |
| `80` | 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. |
| `MAX_UPLOAD=<5000>` | To set maximum upload size (in MB), default if unset is 5000. |
### Volume Mappings (`-v`)
| Volume | Function |
| :----: | --- |
| `/config` | Where to store projectsend config files. |
| `/data` | Where to store files to share. |
## 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:
