Announcing “Pitch-burgh”, an innovation contest at DrupalCon Pittsburgh, where members of the Drupal community can pitch their ideas to receive funding.
[…] The entrepreneurs give short 2-3 minute presentations in the hopes of securing funding for their idea.
As mentioned in the first part of the series, our
most recent work on Aegir5 itself has been reworking the queue system. In this
post, we explore this topic in more detail.
The Aegir5 queue is implemented using
Celery, which is a full-featured
Python-based task queue, built atop RabbitMQ. Initially we built dispatcherd
which …
In our previous post, we looked at the Tasks
and Operations which form the building blocks for the user interface in Aegir5.
Here we’ll look at the additional entities required to support the
Kubernetes-based backend framework.
It is worth noting that Aegir has always had a tension between Developer and
SysAdmin use-cases. We’ll cover this in more depth in a later post. For the
moment, we’re focused on the Developer use-case.
In our previous post, we talked about our recent
client work building a Kubernetes-based system for hosting web applications.
We’ve defined a general framework to support our development and production
hosting workflows, and recognized this as a solid basis for an alternate
backend to plug in to the existing Aegir5 front-end. Today we’ll take a look at
the Drupal architecture underlying that front-end.
In Aegir5, the building blocks consist of Task and Operation entities. Tasks …
Aegir5 development is happening! We (Consensus) have been making steady
progress on it over the last few years and are looking to kick off a new burst
of focused development. Here’s a summary of progress that has been made so far
and how you can contribute.
First off, as you’re probably aware, Aegir5 is a
complete re-write of Aegir. We are intending to build on all the great aspects
of Aegir, while freeing ourselves from a
codebase that is rooted in PHP 4. We’re using D9+ …
