mirror of
https://github.com/projectsend/projectsend.git
synced 2026-09-30 07:41:05 +00:00
ignacionelson
acab833b72
The README now opens its instructions before the screenshots, and says what the quick start assumed: Docker Engine with Compose installed, your own user in the docker group (so nobody reaches for sudo), and which directory the commands run from. The quick start also saved the file as compose.example.yaml and started it with -f. Every later command in DOCKER.md, UPDATE.md and the migration guide is a plain `docker compose ...`, which only finds a file called compose.yaml, so each of them failed with "no configuration file provided". It is now saved as compose.yaml, as the Docker Hub page already said, with one line for people who kept the old name. The migration guide covered "Legacy on this machine, ProjectSend in Docker" in one sentence. It now has a worked route through a bundle. The exporter runs with the host's own PHP, where Legacy's `localhost` database really is local, so no container networking is needed. The guide also says why Direct is harder there: the database, and hardlinks that cannot cross a mount. Step 2 was run against a real v1 install on the host (60 files, 63 MB). Reported by @lukatong (#1635), with the install and migration gaps pointed out by @jjoelc.