The 2026 Drupal Business Survey is open. Your response will help shape the future of the Drupal business ecosystem.I discovered this cool DrupalAPI building install profile, that also appear to support adding additional extensions. It'd be great to add this capability to the utility VM, or possibly just as its own blueprint.
Comments
Comment #1
ergonlogicSo, first off, the utility VM currently resides in aegir-up. But since it might make more sense for it to be its own blueprint, I guess I'll just leave this here for now. Added a 'Blueprints' component, since that'll likely be somewhat common.
Comment #2
decipheredHi there,
I'm the developer to the DrupalAPI distro, and I have been meaning to look into Vagrant for sometime (mainly as a means of Aegir development), but I did stumble onto this issue.
While I understand the desire for this to go into the Utility blueprint, I almost see the more important thing being a simple way to invoke any distro from the drupal-up command, where you simply do something like:
drush drupal-up [distro]
Just a thought.
Comment #3
ergonlogicHmm, that's a good idea. I added #1854048: Build distros from the cli as a feature request against drupal-up.
The reason I've been thinking of adding this to the 'utility' blueprint was so as to have a private API site that could include arbitrary contrib and custom modules. But maybe it would be better on a per-project basis. Ideally, we could pass it the makefile we're using for our platform, and populate the API site with all and only the components we need for the project.
Comment #4
decipheredThat's a really interesting Idea, I do like that indeed.
I have been thinking about making it possible to to have an interface during or after installation to add additional contrib module to the API, so something like this appeals to me greatly.
If you can do most of the vagrant side of things I can work on any modifications required to the DrupalAPI distro.