Documentation

Architecture of subdomains for different sections/departments sharing maximum number of tables
http://drupal.org/node/54649

consen - http://drupal.org/user/13462
http://consen.org/

We have the Editorial sections sharing the tables
$db_prefix = array(
'default' => 'EXTRA_',
'users' => '',
'sessions' => '',
'role' => '',
'authmap' => '',
'sequences' => '',
);
and the Drupal files in the subdomain extra.mainsite.org

This same we have done for the administration section
admin.mainsite.org
and for the Office section
office.mainsite.org

http://dave.notik.com/contact

Hello Dave,

I'm going to be attempting to do pretty much exactly what you describe in "Drupal for my family" http://drupal.org/node/18023

...
need this "single site with subsites with different blocks and themes" functionality.

If you've kept up with the various new options (multidomain: http://drupal.org/project/multidomain settings.php hardcoded themes, split databases, Organic Groups, where Sections is at...) and you want to take another crack at a multi-section site, we can definitely find some money to avoid evaluating all that ourselves.

5.0 Themes

Allegedly Foundation theme is also 5.0, and "the best starting place" according to someone at DrupalCampNYC...

(+ means included in Agaric's site recipe generator)

• http://drupal.org/project/bluebreeze - based on Zen ("the starting point theme") but farther along to looking awesome

• http://drupal.org/project/sinatra - A very solid rewrite of Bluemarine

Consider:
+ http://drupal.org/project/aberdeen
Liquid CSS layout (tableless)

• http://drupal.org/project/amadou

Drupal 5 contributed modules as of 2007 January 29

(+ means included in the default Agaric's site recipe creator)

+image
+http://drupal.org/project/image

+imagecache
http://drupal.org/project/imagecache

+http://drupal.org/project/article

(Drupal 5 as of 2007 January 29)

To Consider:
http://drupal.org/project/biblio
It closely follows the EndNote model: http://www.endnote.com/
* EndNote and bibTex import / export
* keyword filtering
* selectable output styles (original, CSE, APA and IEEE so far)
* admin selectable "base" URL (you can change "/biblio" to anything you want)
* full text entry field; you can now enter the full text of the publication (Text or HTML) and it will be displayed when the user views the biblio node.

See http://liiscience.org/biblio for a live example.

After trying a lot of stuff that didn't work, like ssh -2 username@example.com:6927 or #6927 and many possible and impossible permutation, and after some internet searching, Agaric Design cobbled together this for your benifit. For those of you on Windows, I think you can just type in the port number. For those of you on Linux or Unix-like systems, this may help. It is tested and approved on Mac OS X:

Edit or create a plain text config (no extension) file in the .ssh (invisible system) folder in you ~/Username/ directory.

So after running Agaric's site recipe generator...

had to do the permissions changing to run the install, these were the commands.

Once I know for sure if we want -rw-r--r-- or -rwxr-xr-x for settings.php I'll post to Agaric about it.

<

pre>
[benjamin@vps conf]$ cd /home/spaceshare/public_html/test/sites/default
[benjamin@vps default]$ ls -l total 7 drwxr-xr-x 2 root root 1024 Jan 29 18:16 CVS -rw-r--r-- 1 root root 6023 Jan 13 21:05 settings.php

sudo vi /etc/httpd/sites.d/example

This will create a new file called example if one doesn't already exist.

(You need an include sites.d/* in /etc/httpd/conf/httpd.conf)

i to edit, this is the model (Agaric hasn't tested the subdomain part quite like this, but for just one directory, even if the domain isn't even pointing at your site yet, the IP will work):

<

pre>
<VirtualHost 101.01.010.10:80>
ServerName www.example.coop
DocumentRoot /home/example/public_html/main
Options Indexes FollowSymLinks
</VirtualHost>

This guide applies to CentOS (a generic version of Red Hat Enterprise Linux, or RHEL) and vsftpd.

There's actually not much reason to give a Linux user FTP access to your entire server; each user can access its own directory, which is fine for user mywebsite. But this can be useful for an admin to create a generic FTP user, with a different username and password from any users with sudo to root capabilities.

cd etc
sudo vi vsftpd/vsftpd.conf

In /etc/vsftpd/vsftpd.conf, uncomment these lines (press i to enter insert/edit mode):

Thanks to Webchick

use subdomains
multi-site setup
using same databases
but hardcode theme and other variables as needed

(How about primary links, blocks, etc?)