http://omega8.cc/import-your-sites-to-aegir-in-8-easy-steps-109
Edited Hint #6
Hint nr 6: When your site’s files directory is big (500MB or more) and you have root access on your server, always symlink large files directory. Aegir by default creates full, compressed archive from entire sites/foo.com directory on every Clone, Migrate, and of course Backup task, so it will fail on servers without enough RAM and CPU power to handle this before PHP-CLI or SQL connection will time out. It is a known issue and there are plans to move files directory away from sites/foo.com by default and only symlink it there, but it is not implemented yet, so you need to use manual workaround for large files directories and move them away, anywhere in the tree, for example to /data/disk/USER/static/domain_files
and thenln -s /data/disk/USER/static/domain_files /path/to/platform/sites/foo.com/files.
Group permissions should also be changed to give www-data write permissions chgrp -R /data/disk/USER/static/domain_files && chmod -R g+w /data/disk/USER/static/domain_files
If you are on the hosted Aegir without root access, contact us to have the files directory symlinked, as explained above.
Original Hint #6
Hint nr 6: When your site’s files directory is big (500MB or more) and you have root access on your server, always symlink large files directory. Aegir by default creates full, compressed archive from entire sites/foo.com directory on every Clone, Migrate, and of course Backup task, so it will fail on servers without enough RAM and CPU power to handle this before PHP-CLI or SQL connection will time out. It is a known issue and there are plans to move files directory away from sites/foo.com by default and only symlink it there, but it is not implemented yet, so you need to use manual workaround for large files directories and move them away, anywhere in the tree, for example to /data/disk/USER/static/domain_files and then ln -s /data/disk/USER/static/domain_files /path/to/platform/sites/foo.com/files. If you are on the hosted Aegir without root access, contact us to have the files directory symlinked, as explained above.
Comments
Comment #1
omega8cc CreditAttribution: omega8cc commentedThanks for the suggestion.
The only problem here is that the how-to is primarily intended for non-root (hosted) users, so they can't use
chgrp
command. Adding this to the how-to could only cause more confusion.I guess that we just need a better distinction, so it will be immediately clear what level of access in needed for particular how-to and where to look for other options/workarounds etc.
Comment #2
omega8cc CreditAttribution: omega8cc commentedAlso, that is why the step #2 says that you need to run
$ chmod -R 777 static/my/sites/default/files/*
so you don't needchgrp
here (and it will be fixed automatically the next morning).Comment #2.0
omega8cc CreditAttribution: omega8cc commentedformatting
Comment #3
omega8cc CreditAttribution: omega8cc commentedYou don't need to set/fix any permissions when you are moving the files directory as-is. In fact, you should never modify any permissions nor ownership there, just move with
mv
(don't copy with cp!) the complete directory and symlink it.