BOA

Summary

I'm working on a backup strategy for our SaaS distro that runs on BOA provisioned cloud vps nodes and I'm looking for feedback. I'll move all of this to a wiki page if it becomes useful and provide the scripts that are currently working for us, as it will be useful for most folk running multiple sites on a single Drupal core.

Use Case

4 question for clarification, please: drush upgrading, and permissions problem - 111 vs 999.

1.) Is it best practice NOT to do a drush based upgrade of Octopus hosted sites from one minor version of Drupal to another?

a very interesting new sandbox project relevant to BOA developers looking for a tool-chain from local dev to stage to prod on BOA systems

<

blockquote>
Ariadne: Vagrant-based Drupal Development Toolchain

Hi, we are using BOA as a development environment and it has helped in many many tasks we used to do automatically while developing Drupal sites.

But one downside we see it's the DB access. We use Chive that is installed by default, it's easy and fast, but each developer (different octopus user) has to login to Chive with different credentials every time he wants to check out a different web site DB.

Would be nice if there is an easy way to display ALL the DBs for all sites that are managed under an octopus user.

Maybe it's already working like that and I'm missing something

What's the best way to remove the old platforms?

I've got a few BOA distributions (if that's the right word - maybe it's install profiles) with a lot of unused platforms. I am now running out of space on my server.

I installed BOA-2.0.3 (http://omega8.cc/boa-203-edition-152) with max platforms.

boa \
in-stable \
public \
myhost.mydomain.tld \
me@mydomain.tld \
o1 \
max \
new-relic-key-1234

I just updated a Debian 6 BOA 2.04 system using "aptitude upgrade". I was under the impression that this is OK after the initial install. When prompted during the upgrade I chose to keep locally modified php.ini files (two times), thinking this would preserve any BOA-specific settings.

Then my Octopus web control panel started throwing occasional errors: 502 Bad Gateway - nginx.

My php53-fpm-error.log showed this: ERROR: unable to bind listening socket for address '127.0.0.1:9090': Address already in use (98)

I am looking for information about how to properly use webmin to setup a new domain in a BOA server - a domain that will not be a drupal site at all.

This is for those of us too poor to have two separate servers and who have to provide for a few non-drupal non-aegir sites on their server.

I know that Webmin can be used to setup a new dns zone for the new non-drupal domain. After that I know that I either manually add a vhost file in nginx or, suppossedly I should be able to use Webmin for this, since webmin is suppossed to support nginx. My questions are as follows:

Hi,

I'm finding that my BOA instance is returning ugly nginx 404s for certain url patterns. Specifically, at the moment, pages that have the word "progress" in the url alias will return a white nginx 404 rather than a relatively nice drupal 404. I'm presuming that I can add a directive in the conf file at /data/disk/EDIT_USER/config/server_master/nginx/post.d/nginx_vhost_include but I just thought I'd see if anyone else has had this issue, and has succesfully altered their setup.

Thanks :)

We held our Broward Drupal monthly meetup on Wednesday, July 11th from 7:00pm to 9:00pm.

Remote participant(via Skype and Join.me):
Seattle - Chris Parsons @chillin411
Stuart - Dustin Cooper @dustinjcooper

In Person (Greater Fort Lauderdale, Broward County Florida):
Jay Epstein @jeppy64, Phil Smith @siliconvalet, Rob de Koter @Robdekoter, Jeff Locke, Elvis Svoboda @ElvisIsOnATrain, Teo Vitkaiskas, Jessica Rivera, Peter Davis, David Gueits, Ben Groenevelt and me @hectoriribarne

This month we had two presentations on Drupal theming, and on installing BOA for managing Drupal sites.