ignacionelson
8156664ccc
The guide had no answer for the install method we recommend most. The published image carries no Composer — it ships the application already built and has no use for one — so `composer require`, the first command in Step 1, is not a thing a Docker reader can run at all. The guide's Docker line assumed the stack in this repository, which builds from source and does have one. Composer is a PHP file, and PHP is what the image is. Fetching it into /tmp for the length of the migration works, and the whole path is verified rather than plausible: the tool installs, all four projectsend:migrate:* commands register with no package:discover run by hand, and the export script the Bundle route needs is where the guide now says it is. Two details in there are load-bearing rather than decorative. `-u www-data` because exec lands as root and a root-owned vendor/ is a problem the application meets later rather than now. `--update-no-dev` because the shipped lock file knows about pest and phpstan, and a production install should not grow a test suite on the way past. The section says plainly that the install lives in the container's writable layer and does not survive the container being replaced. That is honest about a real limit, and the reason it is acceptable is worth saying too: the run's progress and its id map are in the database, so losing the package costs an install, not a migration. Step 1 is now three self-contained sections rather than one set of commands with exceptions bolted on, because the previous shape is what let a reader follow instructions that could not work on their install. Verified against the real image, built locally from the release zip — the Docker Hub repository is still private, so pulling it was not an option. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
ProjectSend
Share files with your clients, from your own server.
ProjectSend is a self-hosted application for getting files to the people you work with. You upload what you want to send, choose exactly who can see it, and each client signs in to their own private page to download it.
No public link passed around by email, no third-party service holding your clients' documents, no per-seat pricing. It runs on your server, and the files stay there.
What it does
For the people you send to
- A private area per client, showing only what has been shared with them
- Sign in with an email address, with optional two-factor authentication
- Search, filter and sort their files; download one, several as a zip, or a whole folder
- Optional comments on a file, so questions live next to the thing they are about
- Email notifications when something new arrives, in their own language
For you
- Resumable uploads that survive a dropped connection, so large files actually arrive
- Organise with folders, categories and client groups
- Share with one client, a whole group, or publicly — and set an expiry date or a download limit
- Thumbnails and previews for images and documents
- Storage quotas per client, and custom fields for the details you need to keep on them
- A full activity log and download history: who got what, and when
For the installation
- Roles and permissions for your own team, so an uploader is not an administrator
- Sign-in the way you already work: LDAP, social sign-in, or plain email and password
- Themes for the client-facing pages and for outgoing email
- 16 languages
- A REST API with scoped tokens and generated OpenAPI docs
- Privacy controls, including GDPR-grade account erasure with a grace period
- Local disk or S3-compatible storage
Screenshots
The dashboard — what is in the installation, and what has been happening in it.
Your library — folders, categories, and who each file is shared with.
What your client sees — only their files, nothing else.
Getting started
With Docker — the quickest path, and the one we recommend.
git clone https://github.com/projectsend/projectsend.git
cd projectsend
cp .env.example .env # set PROJECTSEND_EDITION=community
docker compose up -d
The app is at http://localhost:8090, and the first thing it shows you is a setup screen that
creates your administrator account.
Before you put real files in it, read DOCKER.md — where your database and uploads actually live, how to move them onto paths you chose, and how to back them up so an upgrade can't take them with it.
Without Docker — for servers where it isn't an option, install from a release zip.
INSTALL.md covers requirements, .env, nginx, the background worker and cron,
updating and troubleshooting. You do not need Composer or npm on the server; the zip ships ready to
run.
Already running it? UPDATE.md is how you move to a new version — one command on Docker, a short sequence on your own server, and what to check afterwards either way.
Coming from ProjectSend Legacy?
The previous generation of ProjectSend lives on at projectsend/legacy. This is a rebuild rather than an upgrade, so moving across is an import rather than an update — install fresh, then bring your old site into it with the migration tool: accounts, clients, groups, categories, folders, files and history.
It never writes to your old install, and any run can be undone with a single command. MIGRATING-FROM-V1.md explains what comes across, the two routes (same machine, or a portable export from a server you can't reach), and the one change your clients will notice: they sign in with their email address now, using the same password.
Contributing
Bug reports, translations and pull requests are all welcome — see CONTRIBUTING.md for how to set up a development copy, what the checks are, and the contributor agreement.
Found a security issue? Please report it privately through GitHub's security advisories rather than opening a public issue.
License
Free software under the GNU General Public License v2, or (at your option) any later version — see LICENSE. Use it, study it, change it, share it.
Commercial licenses are available for organizations that cannot work under copyleft terms; LICENSING.md explains both options. Contributions require signing a CLA, for reasons set out in CONTRIBUTING.md.