Installing sites in sub-directories is supported in Aegir 2+ without any such hacking. Just enable the "Site subdirectories" feature, under the 'experimental' group at admin/hosting/features.
That said, to answer your question, DB credentials are available via drush_get_context('site').
I would recommend that you avoid multisite, and clone the code into a separate codebase -- then copy the database. This is much easier to manage for simple use cases, and would entirely avoid your problem above, as you would only have one copy of each module present in your code base, so Drupal would not be able to load any of them twice.
I am not sure ...
The cause of above error is that @sites is returning no sites.
Try drush sa @sites too, and see what it says.
Note, however, that @sites refers to all of the sites in a multisite install; it does not refer to all of the sites in your aliases.drushrc.php. If you rename your aliases file to foo.aliases.drushrc.php, then @foo will reference all of the ...
Sounds like you might be looking for the Domain Access module
The Domain Access project is a suite of modules that provide tools for running a group of affiliated sites from one Drupal installation and a single shared database.
You can try drush archive-dump default,example.com,foo.com command to archive the DB and codebase. If it is not possibel through it, then you can create a shell script, which creates backup of the codebase and database.
You can use Domain access module.
The Domain Access project is a suite of modules that provide tools for
running a group of affiliated sites from one Drupal installation and a
single shared database. The module allows you to share users, content,
and configurations across a group of sites such as:
The 'Drush make option' field in the Aegir user interface (when creating a new platform based on a makefile) simply determines whether or not the --working-copy option is passed to Drush make.
The --working-copy option for Drush make "preserves VCS directories, like .git, for projects downloaded using such methods." (source: Drush.org)
Passing the --...
Disclaimer: I use Aegir 2.x and never use the Drupalgap but I use root base files.
Create a new platform in Aegir (don't mess with the current platform) and create a new site.
After that you must have something like: /var/aegir/platforms/platform_name/sites/new_site.com/
If you put your files in /var/aegir/platforms/platform_name/my_folder/my_script.js you ...
Consider starting from a Base theme, such as Omega, Zen, Bootstrap, etc. Or build your own (custom) theme that you can use as a Base theme (that would be youru "core theme".
And then create Sub-themes (that would be what you named "their custom themes").
Note: the question about "Right way to start with a Bootstrap subtheme?" contains a lot of details to ...
In general, you shouldn't use Drush for that. Instead, use a build process, and one of the steps in the build would be drush make.
There are a number of existing build systems that can be used to achieve what you're looking for, including (but not limited to):
Phing - https://www.phing.info/
Jenkins - https://jenkins-ci.org/
Grunt Drupal Tasks - https://...
You're getting the error "MySQL server has gone away". Usually when this happens during Drupal installation, it's related to MySQL's max_allowed_packet setting. I'd recommend bumping that value up to 32MB. The process for changing that value on Amazon RDS is detailed here: https://survivalguides.wordpress.com/2012/02/02/change-the-max_allowed_packet-amazon-...
This is a great question! I maintain both Aegir and Drush Make, but I'm not certain that I have a really good answer for you.
I think that you're suggestion in (1) is probably the best bet at
the moment. It has the virtue of already working, as you've
mentioned. The issue with accidentally merging these [branch]
attributes is still valid though. The ...
Navigate to Hosting » Settings » Task Logs to Display and you can check/uncheck the boxes for the different types of log messages.
As Add proper UX to the selector for choosing logs types to show is fairly new (see that issue for background), it hasn't made it into a release yet so you'll probably still see the text area.
You could implement a drush_hook_pre_COMMAND() hook in drush to run any code you'd like.
See the docs page for more details: https://docs.aegirproject.org/extend/altering-behaviours/#running-extra-code-after-a-task
The Aegir documentation states that root access is required for
installation, but I have seen comments suggesting it is possible to
instal without root. If this is correct can anyone point me in the
In addition to the installation and configuration of web and database servers, the standard installation of Aegir requires the creation of a ...
It's Drupal, so yes you can add an extra field to the site content type on /admin/structure/types/manage/site/fields.
Warning: you must enable first the field_ui module, as it's disabled by default in Aegir installation profile.
I started a documentation page about this: http://docs.aegirproject.org/en/3.x/extend/frontend/
Disclaimer: I do not use Acquia and don't know their service.
Should I need to move the code as a normal multisite setup to Acquia?
The documentation seems to say that multisite is supported: https://docs.acquia.com/cloud/multi-site
You would probably need to copy the platform from /var/aegir/platforms. If you look in that directory, each directory is ...
As I mentioned in IRC, the following work-around should resolve that particular issue:
Login to the server via ssh.
Become the 'aegir' user (sudo -u aegir -s -H)
Create a file call /var/aegir/.drushrc.php with the following contents:
$options['strict'] = 0;
That said, this appears to be a bug, though not one that has been reported previously. ...
If you're interested in managing different branches, please have a look how this is achieved in ADS distribution (GitHub).
Basically you can set-up CI to load the file appropriate for specific branch, e.g.:
then in this file you can have specific components of specific branch (e.g. profile) and everything else (e.g. common ...
Consider using composer which could be a bit more flexible regarding the recursive dependencies as it can analyze the whole dependency tree which you can set-up and many more.
See example composer.json:
The hostmaster-install command has options for --profile and --makefile.
I use these options for OpenDevShop, which has it's own makefile and profile.
You can use a URL or a path for makefile option.
drush hostmaster-install --makefile=/path/to/mymake.make --profile=mycustomprofile