Posts by Month

Posts by Month

Mobile Dev Environment

/base/(head)|(stable)

  • Core system + select essential contribs
/sites/[name]
  • Drupal sites dir for each site.
    • settings.php
    • database.mysql (prod snap)
    • themes
    • modules
  • ACLs prevent snooping.
The auto database backup feature needs some thought. Database/sitename.mysql should always be a recent copy of the production database for the site. The main question is, when are backups made? I'd backups to be user-driven rather than timed. Ideally, checking out a new copy of the site should result in the creation of a db backup. Unfortunately, hooks are only fired on commit, not checkout. Since there are so many questions, we should start simple. I'll just make a script which parses $1/settings.php for $DB params, dumps to $1/database.mysql, and commits $1. Simple and useful. It may be necessary to play with the diff settings to get reasonable patch sizes.


Great things are a foot?

So alot has been happening behind the scenes since my last blog update. I have a beefy new Ubuntu virtual server, which I have been industriously whittling into a kick ass Drupal hosting and development environment. The component which ties the whole system together is the Subversion repository. Whenever a new site branch is created in subversion, a hook is fired which automagically configures Apache and mysql. Sweet! Anyway, I'm working hard on launching some new services, in particular a business homepage with project management, documentation, etc. Cheers


Per-site VS Global branches

Ok, we're discussing repos structure here. The question is, given Drupal's builtin per-site config dirs, are per-site SVN branches useful? It is possible, for instance, to put site-specific mods in the sites dir. Whether dev versions of mods which already exist in the global mods dir will consistently override the global copy, I don't know. Let's check… [opens editor] ^v^v^ Yes! (includes/bootstrap.inc function drupal_get_filename). So there would seem to be no reason to mainain seperate branches for each site. Awesome! The other thing is access control on the sites dirs. So we have two (or three) branches: prod, test, dev. In each branch we have implemented some acls so that you only get the site dir if you pass muster. That sounds hard. So maybe we store the sites in another repos path. Then you need to explicitly check out the site. And each site is ACLed. Frito pie!


Math Forum

I've been operating a forum site for my topology class. I'm planning to commercialize it. I just need a domain and a few additional features. I'm planning to update and improve the latexrender module to work properly with 4.7. It provides a filter to convert inline latex math text into images. This will of course be extremely useful for a math forum.

Update!

Daniel Gutekunst has picked up a google summer of code project to develop thorough LaTeX integration for Drupal. He calls his module Drutex. Cute :)