After successfully installing/running Barracuda & Octopus on a local environment, I'm wondering about the best way to handle several servers for various platforms.
I'm currently working on a site with a huge files folder ( around 12Gb ). In order to avoid having to copy that amount of files between versions, I use symlinks to an external files folder, for instance:
/data/disk/o1/static/files //files folder
/data/disk/o1/static/platforms/dev-platform-1/sites/example-site-v1/sites/ --->/data/disk/o1/static/files
/data/disk/o1/static/platforms/dev-platform-2/sites/example-site-v2/sites/ --->/data/disk/o1/static/filesbut when the css & js caches get updated, it messes up the sync between one of the sites and the files folder. I probably could fix this by not using symlinks for the cache folders... but this is the situation that led me to try and have a setup with a healthy level of separation between stages, whilst retaining the ability to move sites across servers & platforms.
How do I achieve this with BOA. To be more accurate, at this point , I can setup several platforms on one Octopus instance or even several platforms spread across several Octopus instances, all this on a single server... but how can I setup a single Barracuda instance with several Octopus platforms across various servers, or one Octopus platform with several platforms across various servers?
What would make more sense? The idea being to retain as much as possible the concept of a central point of control over a network of servers/platforms.
Also, since each BOA scripts comes bundled up with all the necessary dependencies ( Nginx, MariaDB etc... ), how do I go about setting up a slave server?
Since I don't have the skills to split the scripts in parts I'm concerned with, I would simply run the Barracuda script on a slave server and follow the Aegir way of adding that server to an Octopus instance, what would you recommend?
Thanks in advance!
Comments
Are you using the same files
Are you using the same files directory for different sites? You should use separate directory per site and symlink them also per site.
Anyway, this problem with big files directories will be gone soon, as anarcat already works on it.
As for remote heads support in BOA, please read this: http://drupal.org/node/1305896#comment-5102094
Yes, using the same directory
Thanks, will do!
I guess , for now, there's no other solution and sharing a single files directory clearly doesn't work.
Also, thanks for the link re: remote heads! I was hoping it would have been possible to push a site from a local VirtualBox setup to a VPS, for instance.
Another example would be of a current client running his sites on a dedicated server, whilst other have their sites on a single VPS and having a central Octopus instance to manage all the sites.
Let's see how things move in the future!
Thanks!