• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

File ownership difficulties

U

unsichtbarre

Guest
When ftp'ing to a domain on Plesk 8.0.1 the files get assigned an ownership of username:psacln, however, files which are dynamically uploaded get assigned apache:apache and any files processed by the root user (me, eg: tar -xzf myfile.....) get 1000:1000.
The only way to enable the client to modify/delete these files is by chown'ing the files manually to the correct ownership of username:psacln.
Is there a way to have Plesk (or apache or PHP) assign ownership based on the domain, not which process is doing the work? It would sure save me a lot of work.

Thanks in advance-

-John
 
To be more specific I would like to set the default ownership permissions so that my clients can delete files that have been dynamically uploaded.
 
edit: ok.. didnt read your first post thoroughly...

It's not so much a problem with plesk as just a general unix issue.

If you are untar'ing using a script, try taking a look at the tar option "--owner USER" to assign ownership to extracted files.
 
Cool, "--owner USER" will save me a ton of time when I unpack archives on my server, but as I am the only one with shell access, I am still faced with my users not being able to delete or modify files that apps like Joomla upload to their domain/client accounts.
The "big boys" (like godaddy)who run shared hosting accounts do not seem to have any trouble keeping all users files set to each users ownership no matter how they were uploaded. I was hoping for the existance of some global, yet unknown to me, configuration setting (some variable in httpd.conf, perhaps) which would keep all my users files in their ownership rather than apache:apache.

Thanks for the continued attention to this issue,

-J
 
Again, that's not an issue with plesk, but the way unix handles file ownership and permissions.

A nightly cron "cleanup" script to check and correct permissions for hosting directories would work for this..

If you are talking about uploading via php scripts, then I'm sure you can find some server options for apache/php that will default uploads to ownership of destination folder, or alternatively, modify your upload script to assign permissions/ownerships based upon destination folder rather than the apache process owner.
 
Back
Top