webschuur.com

This is a morphological overview, to display all te options for deploying a Drupal (and/ or Joomla!! or any other CMS) hosting system.

The way one should read it

In the first vertical column all “tasks” we need to perform are listed, chopped up into the smallest possible unit. Then next to each of these we render all possible tools and solutions for each task, without taking in consideration how ill-suited these tools may be, nor how well they can, or will co-operate. By refusing to look at possible solutions yet, we can make sure that we actually list all options.

Sympal Scripts Premature manual

It is a bit strange to write a manual before the features in that manual are all implemented, but I think it is an interesting workflow, to start off with documentation, because it gives me (developer) and my audience (potential users) a clear view of what Sympal Scripts will do. And it shows a clear todo for me too. Below are the common usage parameters and usage concepts. In reality some of the commands can take a lot of advanced parameters in addition to the listed command parameters.

Usage:

install.php        Install new features in a multisite, or a new site.
 --type [site|module|theme]        Site installs a new multisite. Module installs a new module
 --variables site=example.com user=Joe email=joe@example.com etc.
                             A name=value list of variables needed for installation of the module or site. Provide none to see a list of required values.
 --fixtures directory-name   Use the fixtures in the directory directory-name to preconfigure the site.
 --dry-run                   Don't write anything, just output information
 --verbose                   Be more verbose

Yesterday David pointed me at a cool screen-cast of the Civicspace (CS) installer. His question was, how much Sympal scripts and its install system could use from and be used by the CS installer. Because I got this kind of questions more often, here is a summary and a small status report.

Here is what I need and what I have resources for:

• Sympal is all command-line based. Consultants and developers have command-line skills. (or else they should get another Job :)) )

Sympal runs in a very secure (no, this is not an invitation ;) ) chrooted server environment. Having it all chrooted is nothing new and it is not too hard all together. Especially if you run on a very well designed system like Debian.

Here are some hints and notes for others looking at chrooting their Drupal environment:

A while ago I presented the community my ultimate solution to the everlasting “Drupal Suxorz Coz it has no Image support”.

Well, first of all: there are a gazillion contribs that deal with this. But even for core this is plain untrue: Drupal can handle files (attachments) very well, and showing them inline is as easy as copy-pasting an HTML tag.

However, in search of an even simpler solution, I decided to create something that is as simple as can be. And if found it in the idea “Just add attached images to the body and teaser, if they can be shown inline”. Simple as can be!

Or, how to get the project rolling.

First of all we need to recognise that there is no Ultimate i18n solution. There are many, all depending on the needs, cases and implementations. So, I really do not believe in a single i18n module. Or in a holy grail. Therefore I torn the problem apart, and made Lego blocks out of it. That way the problem becomes rather clear.