WARNING: This website is obsolete! Please follow this link to get to the new Albert@Home website!
Server code upgrade aftermath: need to postpone Drupal migration
Joined: 4 Sep 07
Last week we announced that we need to conduct the general server code upgrade before we can begin with the Drupal migration. As you might have read, we finally managed to upgrade the BOINC server code this week. However, it turned out that we were able to migrate the daemon- and database-related parts "only" so far. We didn't yet manage to upgrade the web code as this turned out to be much more complex than anticipated because, over the years, our codebase diverged significantly from upstream. That means we need to reassess the situation in a very detailed analysis. We might use this opportunity to reconsolidate our separate web code repository with the original upstream repo to facilitate coherent updates in the future.
All this means that we have to postpone the Drupal migration until we merged/upgraded the BOINC web code as well. You might think: "why do you have to update the BOINC web code when you plan to move to Drupal anyway?" Well, the BOINC web code comprises more than just the web front-end (eg. client RPC APIs) and Drupal still depends on a few of those features.
Sorry for the bad news. We're eager to get Drupal deployed but we need to have a stable foundation in terms of the regular BOINC server infrastructure first of all.