Are there any specific good habits to learn?

?How to avoid issues with files/directories access permissions, breaking later even some Aegir task like site clone/migrate, and how to fix them?

!While most of this is already automated, and permissions even fixed automatically every morning by our autonomous maintenance system (but only when there is at least one site in the platform), there are still some things you should be aware of, to make your work easier and avoid headaches. Below we will post updated from time to time list of good habits. Note that when you are using FTPS (FTP over SSL) or SFTP (FTP over SSH) access to upload files, all permissions should be set atomatically for you, on the fly – but only for “modules”, “themes” and “libraries”, while all uploaded subdirectories of the “files” directory still require manual chmod -R 777. Also, some SFTP clients don’t respect default system umask, so you should always check permissions on the uploaded/transferred files and directories. The problem is mostly with files and directories rsync-ed or extracted from archives on command line, or downloaded with Drush.

• Always chmod -R 775 all modules and themes when uploaded via SSH or Drush.
• Always chmod -R 777 all files uploaded to the sites/domain/files directory.
• Never clone/migrate/restore the site if you didn’t chmod uploaded files/directories first.
• Re-Verify the site in Aegir after uploading your modules and themes.
• Run Verify task on every site and platform after modules updates.
• Run Verify task on site and its platform before running Clone task.
• Run Verify task both on the original and cloned sites again after running Clone task.
• Run Verify task on site and both platforms (source and target) before running Migrate task.
• Use Migrate task to rename the site (domain).