This website is composed of information connected through taxonomy. It is simultaneously a proof-of-concept and a means to allow Agaric to share and store information both within the collective and the world as part of our open documentation philosophy.

User login

This website is composed of information connected through taxonomy. It is simultaneously a proof-of-concept and a means to allow Agaric to share and store information both within the collective and the world as part of our open documentation philosophy.

Get Real Step by Step

Brainstorm

Come up with ideas.

Paper sketches

Sketches are quick, dirty, and cheap and that's exactly how you want to start out. Draw stuff. Scrawl stuff. Boxes, circles, lines. Get your ideas out of your head and onto paper. The goal at this point should be to convert concepts into rough interface designs. This step is all about experimentation. There are no wrong answers.

(I've never understood how, let alone why, to make brainstorming and sketches separate steps.)

Brainstorm

Come up with ideas.

Paper sketches

Sketches are quick, dirty, and cheap and that's exactly how you want to start out. Draw stuff. Scrawl stuff. Boxes, circles, lines. Get your ideas out of your head and onto paper. The goal at this point should be to convert concepts into rough interface designs. This step is all about experimentation. There are no wrong answers.

(I've never understood how, let alone why, to make brainstorming and sketches separate steps.)

Create HTML screens

Basic Mail Debugging

Mail doesn't work? Not receiving e-mails? Any of those problems, don't do what I did: start with some basic mail troubleshooting:

You may want to check your /etc/syslog.conf file (vi /etc/syslog.conf) to make sure it's doing this:

# (- Log all the mail messages to one place.)
mail.* -/var/log/maillog

If so, then check out that log!

You can go directly to the end of it:

sudo tail /var/log/maillog

Mail doesn't work? Not receiving e-mails? Any of those problems, don't do what I did: start with some basic mail troubleshooting:

You may want to check your /etc/syslog.conf file (vi /etc/syslog.conf) to make sure it's doing this:

# (- Log all the mail messages to one place.)
mail.* -/var/log/maillog

If so, then check out that log!

You can go directly to the end of it:

sudo tail /var/log/maillog

(Sudo may be required if you aren't logged in as root, which you shouldn't be.)

Still more Getting Real

Continued from More notes on Getting Real.

Human Solutions

Build software for general concepts and encourage people to create their own solutions

Don't force conventions on people. Instead make your software general so everyone can find their own solution. Give people just enough to solve their own problems their own way. And then get out of the way.

From "Human Solutions"

More notes on Getting Real

Continued from First Notes on Getting Real, a book by web app company 37 Signals.

Differentiate yourself from bigger companies by being personal and friendly

Hell, we're all over that one.

From "Be Yourself"

What's the Big Idea

Before you start designing or coding anything you need to know the purpose of your product — the vision. Think big. Why does it exist? What makes it different than other similar products?

Create Mailman list through the command line

On a Dedicated or Virtual Private Server:

You can use the locate command to discover where your newlist file lives:

locate newlist | grep -v template

And so then:

# /usr/lib/mailman/bin/newlist [email protected]
prompt > Enter the email of the person running the list:
prompt > Initial mailman-test password:

And place the text it generates into /etc/aliases or its equivalent on your system. With Postfix installed, for instance, you might need to paste that text into /etc/postfix/aliases (even though /etc/aliases exists.)

Creating Mailman users who can create lists

[It's easier to create mailman lists through the command line.]

Creating a list at:
example.com/mailman/create

Gives the error:
You are not authorized to create new mailing lists

Which isn't a very nice thing to say.

(where does the user log in, what kind of user rights must have)

From a forum post asking the same question:

[It's easier to create mailman lists through the command line.]

Creating a list at:
example.com/mailman/create

Gives the error:
You are not authorized to create new mailing lists

Which isn't a very nice thing to say.

(where does the user log in, what kind of user rights must have)

From a forum post asking the same question:

<

blockquote>

I am running RH ES 3 and installed the mailman rpm. Every time I try to
create a list it give me this error:

Error: You are not authorized to create new mailing lists

Multiple aliases in Drupal

[To put this in something more resembling English, we're talking about creating multiple URLs, more than one web address, to one page or piece of content on a Drupal site.]

It's actually very easy. Go to admin/path/add and add another alias for the node which you want multiply aliased.

(Look up the node/## first by going to the node, and checking the node/##/edit path– you'll have to be logged in to see the edit link.)

So if it's that simple, why would this need an explanatory page on Agaric Design?

[To put this in something more resembling English, we're talking about creating multiple URLs, more than one web address, to one page or piece of content on a Drupal site.]

It's actually very easy. Go to admin/path/add and add another alias for the node which you want multiply aliased.

(Look up the node/## first by going to the node, and checking the node/##/edit path– you'll have to be logged in to see the edit link.)

So if it's that simple, why would this need an explanatory page on Agaric Design?

Mailman set-up and configuration

NameError: name 'subdomain' is not defined<code> 

In mm_cfg.py the lines need quotes ('), for instance:

<code>DEFAULT_URL_HOST = 'subdomain.example.com'

NameError: name 'subdomain' is not defined<code> 

In mm_cfg.py the lines need quotes ('), for instance:

<code>DEFAULT_URL_HOST = 'subdomain.example.com'

GNU-Linux Command Line Resources

Overview, features, shortcuts

Grid of commands

File permissions (see also file and directory ownership commands)

Overview, features, shortcuts

Grid of commands

File permissions (see also file and directory ownership commands)

Segmentation fault 11 error – Voodoo Zoodoo

A problem we dealt with that we very much hope no one else ever sees: a brand new virtual private server install, CentOS, Apache, PHP5, and Webmin, and everything worked except our Drupal site, which came up completely blank.

I am getting a seg fault when I try and run. this line is showing up in the apache error log

'exit signal Segmentation fault (11)'

anyone familiar with this?

here are some drupal notes:

http://drupal.org/node/63181

A problem we dealt with that we very much hope no one else ever sees: a brand new virtual private server install, CentOS, Apache, PHP5, and Webmin, and everything worked except our Drupal site, which came up completely blank.

I am getting a seg fault when I try and run. this line is showing up in the apache error log

'exit signal Segmentation fault (11)'

anyone familiar with this?

here are some drupal notes:

http://drupal.org/node/63181

http://drupal.org/node/57783#comment-167102