The script also copies fileconveyor.sh into /var/fileconveyor, where fileconveyor.sh has its modes changed so that it runs as apache. var/fileconveyor is also where all of the database files for Fileconveyor are stored.
This script made a standard layout for all of the servers with the Fileconveyor code in /var/fileconveyor. In order to setup Fileconveyor the same way across all of the servers, we made a script:. I still suggest that you try Fileconveyor as it works well with the Drupal CDN module however, you must be mindful that certain modules might affect the behavior between the filesystem and Drupal.Īlso, all servers leveraging fileconveyor must be set up the same for proper functionality. The symptom: files were not being written to the filesystem! Aack! The issue: Fileconveyor uses inode-notify and the "link" call to the file system would not give the whole inode chain, or as least not in Python2.6 as of Linux Kernel:Ģ.6.32-358.23.2.el6.x86_64 #1 SMP Wed Oct 16 18:37: x86_64 x86_64 x86_64 GNU/Linux
If you write a single file, we had no issues at all with Fileconveyor however, we found that we had issue when applications wrote to a file that was embedded in a new directory structure. Fileconveyor either works great or it does not work based on how the application writes files to the directory. If you use Drupal, Magento, Wordpress, etc on Rackspace and want a CDN, they will suggest to you to use Fileconveyor. I recently was tasked with debugging a deployment issue with the CDN on Rackspace. for contributing his experience after a battle with Rackspace, Fileconveyor, Drupal, Linux, and inodes. Thank you to our guest author, Brian Degnan, PhD.