Richard G
Verified User
Now I'm totally confused. My users don't have SSH so they don't use commands in CLI, or maybe via php file but the docs and describtion makes it too confusing for me now.
Why not use php-fpm's chroot directive for this? That's already built into php-fpm.
Why not use php-fpm's chroot directive for this? That's already built into php-fpm.
You have bubblewrap already.
You'd just have to build a chroot'd directory environment for every user and then set each user's php-fpm pool to their respective chroot'd directory.
I haven't had a chance to test any of this, but I'd think the memory requirements would be a lot less.
Now I'm totally confused. My users don't have SSH so they don't use commands in CLI, or maybe via php file but the docs and describtion makes it too confusing for me now.
I just worry that every user having their own systemd php-fpm configuration is an over complication of the setup. And the more complex something is, move one rock and the whole building falls down.
+ it is not as nice as separate php-fpm master processes with complete isolation using namespaces, and dedicated process management inside their own cgroups![]()