0

what do i have to keep iin mind ? what do i have to take care for - especially if i have troubles with

  • file ownership
  • permissinos

if i set up a drupal-commons version 6.25 locally on my machine at home - which is a openSuse 12.1 - everything runs nice. All goes smoothley. especially if i want to upload files - no problem here-

but if i wantto do the same - /uploading pictures - on the version that i either installed directly on the webserver or portet over to the webserver i have terrible issues. i it is not possivble to upload any file - i have trouvbles and get error messages....

regarding the temp-directory (wich is complained to b emissing) regarding the permissions on site/default/files

well some words regarding the server and the circumstanceds and conditions it runs with: my serveradmin works with the setgit bit

I run a linux sever that is administered by a friend of me. He prepares the chown and permissins - with the setgit-bit to on. See the issues with the server described more detailed here

on a sitenote: Well the trouble is that i get lost the setgitbit every time when i touch the permissions with FileZilla. That is the terrible issue! Note - at the moment i do not have a access to the server wit WinSCP - winscp can set the Setgit. Filezilla cannot do this at all!

well the question is: what do i have to take care for if porging over the drupal. both versions

.a a drupal commons version 6.25 and .b a drupal version 7.12

do i have to set up a tmp directory again note: if i create the whole installation here on my local server then my assumption is, that all things have been done propperly

what experience do you have - what do i have to take care for?

well i love to see a fruitful discussion

2

I strongly recommend you look into using drush to synchronise sites. Although it admittedly will not solve your permission woes, it will greatly ease the pain of doing this for every update you need to push.

As for permissions, there are many ways of configuring depending on your set-up and how safe you want to be. I usually just have all files belong to webserver and add my user to webservers group, but like I said many things can go wrong with permissions.

Coming back to drush rsync, I would most probably attack this by setting up 2 aliases, one for @dev and the other one for @live (or @stage). So, with those aliases you can rsync via the simple command drush rsync @dev @live your whole site will be transferred. Just set proper permissions the first time you do this on /files and other folders needing write access, and you should be set to go.

PS: Do look into drush sql-copy and other goodies hidden in drush. I cannot imagine doing this manually anymore, I have used aliases for a few years now and would NOT go back the old way!

Hope that helps, good-luck!

| improve this answer | |
  • HELLO dear steffgosselin - manymany thanks! i will take all your advices into consideration - especially the drushed ones;-) – zero Mar 18 '12 at 18:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.