On 9/1/20 8:05 AM, ITwrx wrote: > Am i missing something about how people are using nginx and php > together, or is this just legacy packaging defaults from a time when > there was only apache, which haven't been reconsidered since then? If > the latter, it would be nice if Fedora would reconsider the way these > packages' users are handled. TL;DR -- can end up pushing rocks uphill. Fedora pkgs' can make some ... interesting ... assumptions. apache deps are just one. for 'fun', install composer from pkgs, and see what comes along for the ride! no thanks. A lot of it comes from pkg-ers trying to build swiss-army-knife pkgs -- all-things-to-all-people. IMO, ends up fitting no one's needs really well. Well, not mine, anyway. Re: "Fedora would reconsider", note that _many_ pkgs are not 'official', but COPR. Maintainers' whims rule; they configure/build at their discretion. Only. _Some_ maintainers are quite responsive/interested & willing to give-/get-help; others, not at all. Alternative options are, generally, (1) live with all of the distro's assumptions & crowbar your infrastructure to fit (2) override init system configs to point to own service configs, including uid/gid (3) roll your own rpms, or build from source, with options as you prefer *my* rule of thumb is to _never_ depend on distros' configs for production use. sure, it's usually 'safe' -- but, often, not-so-much ... for reasons such as you mention. for me (1)'s out. i've had far too many 'config surprises' over the years -- both within distros' upgrade & across distros instead, i typically use a mix of (2) & (3) in my case, for php-fpm, the available distro-rpms' build config's to my liking, so I use (2). i install the rpms, simply ignore the (admittedly annoying) installed apache dependencies, and then override the systemd unit, cat /etc/systemd/system/php-fpm.service.d/override.conf [Service] Environment=PHPRC=/usr/local/etc/php Environment=PHP_INI_SCAN_DIR=/usr/local/etc/php/conf.d Type=forking PIDFile=/run/nginx/php-fpm.pid ExecStart= ExecStart=/usr/sbin/php-fpm \ --pid /run/nginx/php-fpm.pid \ --fpm-config /usr/local/etc/php/php-fpm.conf to point to my own php-fpm config, which includes, in my case ... [www] listen = /run/nginx/php-fpm.sock listen.allowed_clients = 127.0.0.1 listen.owner = wwwrun listen.group = www listen.mode = 0660 user = wwwrun group = www ... and, as per the Environment=, points to my own php configs. otoh, for nginx, i'm not a fan of available distro builds, so I build my own rpms. i install *my* rpms, 'mask' default units in the /usr/lib/systemd/system location (just in case, again to avoid surprses), & create my own full .service/.target/tmpfile the units et al set uid:gid to my liking; in my case, wwwrun:www. i then rinse-n-repeat similarly for any/all other production services. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
