The `--sort` argument to ls is a linuxism (more precisely a
gnu-coreutilsism). I get this output when attempting these
instructions on FreeBSD (13):
$ diff -u "$(ls --sort=t | head -2 | tail -1)/config/production.yaml.example" "$(ls --sort=t | head -1)/config/production.yaml.example"
ls: unrecognized option `--sort=t'
usage: ls [-ABCFGHILPRSTUWZabcdfghiklmnopqrstuvwxy1,] [--color=when] [-D format] [file ...]
ls: unrecognized option `--sort=t'
usage: ls [-ABCFGHILPRSTUWZabcdfghiklmnopqrstuvwxy1,] [--color=when] [-D format] [file ...]
diff: /config/production.yaml.example: No such file or directory
Changing `--sort=t` to the POSIX-compliant `-t` makes this work as
expected and operates just fine on Linux (tested on Fedora Linux 39).
Fixes#6412
* Update production.md
On Ubuntu 22.04, the dir `/var/www/peertube` is restricted to user peertube & group peertube. This causes issues with many of the subsequent sudo commands, and also results in white-screen on initial visit to the site due to JS files not being accessible. This PR loosens those requirements, but maybe would be better if nginx is just added to peertube group? This is my first time installing PeertTube, so I'll defer to someone with more knowledge of this framework to vet the approach here.
* Set specific mode on peertube root directory
* Minor fixup
* Prefer ls instead of chmod to check directory
Co-authored-by: Chocobozzz <me@florianbigard.com>
- support/docker/production/docker-compose.yml: addition of a nginx
image reusing support/nginx/peertube nginx conf to improve performance,
and lessen setup differences between the docker-compose install and the
typical production install.
- support/docker/production/docker-compose.yml: postgres 10 -> postgres
12, redis 4 -> redis 5. Postgres major updates implies manual upgrade.
- support/nginx/peertube: HTTP -> HTTPS redirection is now commented
by default, to allow its reuse in support/docker/production/docker-compose.yml.
