5 StatusNet 0.9.0 ("Stand")
8 This is the README file for StatusNet, the Open Source microblogging
9 platform. It includes installation instructions, descriptions of
10 options you can set, warnings, tips, and general info for
11 administrators. Information on using StatusNet can be found in the
12 "doc" subdirectory or in the "help" section on-line.
17 StatusNet is a Free and Open Source microblogging platform. It helps
18 people in a community, company or group to exchange short (140
19 characters, by default) messages over the Web. Users can choose which
20 people to "follow" and receive only their friends' or colleagues'
21 status messages. It provides a similar service to sites like Twitter,
22 Google Buzz, or Yammer.
24 With a little work, status messages can be sent to mobile phones,
25 instant messenger programs (GTalk/Jabber), and specially-designed
26 desktop clients that support the Twitter API.
28 StatusNet supports an open standard called OStatus
29 <http://ostatus.org/> that lets users in different networks follow
30 each other. It enables a distributed social network spread all across
33 StatusNet was originally developed for the Open Software Service,
34 Identi.ca <http://identi.ca/>. It is shared with you in hope that you
35 too make an Open Software Service available to your users. To learn
36 more, please see the Open Software Service Definition 1.1:
38 http://www.opendefinition.org/ossd
40 StatusNet, Inc. <http://status.net/> also offers this software as a
41 Web service, requiring no installation on your part. The software run
42 on status.net is identical to the software available for download, so
43 you can move back and forth between a hosted version or a version
44 installed on your own servers.
49 This program is free software: you can redistribute it and/or modify
50 it under the terms of the GNU Affero General Public License as
51 published by the Free Software Foundation, either version 3 of the
52 License, or (at your option) any later version.
54 This program is distributed in the hope that it will be useful, but
55 WITHOUT ANY WARRANTY; without even the implied warranty of
56 MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
57 Affero General Public License for more details.
59 You should have received a copy of the GNU Affero General Public
60 License along with this program, in the file "COPYING". If not, see
61 <http://www.gnu.org/licenses/>.
63 IMPORTANT NOTE: The GNU Affero General Public License (AGPL) has
64 *different requirements* from the "regular" GPL. In particular, if
65 you make modifications to the StatusNet source code on your server,
66 you *MUST MAKE AVAILABLE* the modified version of the source code
67 to your users under the same license. This is a legal requirement
68 of using the software, and if you do not wish to share your
69 modifications, *YOU MAY NOT INSTALL STATUSNET*.
71 Additional library software has been made available in the 'extlib'
72 directory. All of it is Free Software and can be distributed under
73 liberal terms, but those terms may differ in detail from the AGPL's
74 particulars. See each package's license file in the extlib directory
80 This is a major feature release since version 0.8.3, released Feb 1
81 2010. It is the final release version of 0.9.0.
83 Notable changes this version:
85 - Support for the new distributed status update standard OStatus
86 <http://ostatus.org>, based on PubSubHubbub, Salmon, Webfinger,
88 - Support for location. Notices are (optionally) marked with lat-long
89 information, and can be shown on a map.
90 - No fixed content size. Notice size is configurable, from 1 to
91 unlimited number of characters. Default is still 140!
92 - An authorization framework, allowing different levels of users.
93 - A Web-based administration panel.
94 - A moderation system that lets site moderators sandbox, silence,
95 or delete uncooperative users.
96 - A flag system that lets users flag profiles for moderator review.
97 - Support for OAuth <http://oauth.net> authentication in the Twitter
99 - A pluggable authentication system.
100 - An authentication plugin for LDAP servers.
101 - Many features that were core in 0.8.x are now plugins, such
102 as OpenID, Twitter integration, Facebook integration
103 - A much-improved offline processing system
104 - In-browser "realtime" updates using a number of realtime
105 servers (Meteor, Orbited, Cometd)
106 - A plugin to provide an interface optimized for mobile browsers
107 - Support for Facebook Connect
108 - Support for logging in with a Twitter account
109 - Vastly improved translation with additional languages and
110 translation in plugins
111 - Support for all-SSL instances
112 - Core support for "repeats" (like Twitter's "retweets")
113 - Pluggable caching system, with plugins for Memcached,
114 APC, XCache, and a disk-based cache
115 - Plugin to support RSSCloud
116 - A framework for adding advertisements to a public site,
117 and plugins for Google AdSense and OpenX server
118 - Plugins to throttle excessive subscriptions and registrations.
119 - A plugin to blacklist particular URLs or nicknames.
121 There are also literally thousands of bugs fixed and minor features
122 added. A full changelog is available at http://status.net/wiki/StatusNet_0.9.0.
124 Under the covers, the software has a vastly improved plugin and
125 extension mechanism that makes writing powerful and flexible additions
126 to the core functionality much easier.
131 The following software packages are *required* for this software to
134 - PHP 5.2.3+. It may be possible to run this software on earlier
135 versions of PHP, but many of the functions used are only available
137 - MySQL 5.x. The StatusNet database is stored, by default, in a MySQL
138 server. It has been primarily tested on 5.x servers, although it may
139 be possible to install on earlier (or later!) versions. The server
140 *must* support the MyISAM storage engine -- the default for most
141 MySQL servers -- *and* the InnoDB storage engine.
142 - A Web server. Preferably, you should have Apache 2.2.x with the
143 mod_rewrite extension installed and enabled.
145 Your PHP installation must include the following PHP extensions:
147 - Curl. This is for fetching files by HTTP.
148 - XMLWriter. This is for formatting XML and HTML output.
149 - MySQL. For accessing the database.
150 - GD. For scaling down avatar images.
151 - mbstring. For handling Unicode (UTF-8) encoded strings.
152 - gettext. For multiple languages. Default on many PHP installs.
154 For some functionality, you will also need the following extensions:
156 - Memcache. A client for the memcached server, which caches database
157 information in volatile memory. This is important for adequate
158 performance on high-traffic sites. You will also need a memcached
159 server to store the data in.
160 - Mailparse. Efficient parsing of email requires this extension.
161 Submission by email or SMS-over-email uses this extension.
162 - Sphinx Search. A client for the sphinx server, an alternative
163 to MySQL or Postgresql fulltext search. You will also need a
164 Sphinx server to serve the search queries.
165 - bcmath or gmp. For Salmon signatures (part of OStatus). Needed
166 if you have OStatus configured.
168 You will almost definitely get 2-3 times better performance from your
169 site if you install a PHP bytecode cache/accelerator. Some well-known
170 examples are: eaccelerator, Turck mmcache, xcache, apc. Zend Optimizer
171 is a proprietary accelerator installed on some hosting sites.
176 A number of external PHP libraries are used to provide basic
177 functionality and optional functionality for your system. For your
178 convenience, they are available in the "extlib" directory of this
179 package, and you do not have to download and install them. However,
180 you may want to keep them up-to-date with the latest upstream version,
181 and the URLs are listed here for your convenience.
183 - DB_DataObject http://pear.php.net/package/DB_DataObject
184 - Validate http://pear.php.net/package/Validate
185 - OpenID from OpenIDEnabled (not the PEAR version!). We decided
186 to use the openidenabled.com version since it's more widely
187 implemented, and seems to be better supported.
188 http://openidenabled.com/php-openid/
189 - PEAR DB. Although this is an older data access system (new
190 packages should probably use PHP DBO), the OpenID libraries
191 depend on PEAR DB so we use it here, too. DB_DataObject can
192 also use PEAR MDB2, which may give you better performance
193 but won't work with OpenID.
194 http://pear.php.net/package/DB
195 - OAuth.php from http://oauth.googlecode.com/svn/code/php/
196 - markdown.php from http://michelf.com/projects/php-markdown/
197 - PEAR Mail, for sending out mail notifications
198 http://pear.php.net/package/Mail
199 - PEAR Net_SMTP, if you use the SMTP factory for notifications
200 http://pear.php.net/package/Net_SMTP
201 - PEAR Net_Socket, if you use the SMTP factory for notifications
202 http://pear.php.net/package/Net_Socket
203 - XMPPHP, the follow-up to Class.Jabber.php. Probably the best XMPP
204 library available for PHP. http://xmpphp.googlecode.com/. Note that
205 as of this writing the version of this library that is available in
206 the extlib directory is *significantly different* from the upstream
207 version (patches have been submitted). Upgrading to the upstream
208 version may render your StatusNet site unable to send or receive XMPP
210 - Facebook library. Used for the Facebook application.
211 - PEAR Services_oEmbed. Used for some multimedia integration.
212 - PEAR HTTP_Request is an oEmbed dependency.
213 - PEAR Validate is an oEmbed dependency.
214 - PEAR Net_URL2 is an oEmbed dependency.
215 - Console_GetOpt for parsing command-line options.
216 - libomb. a library for implementing OpenMicroBlogging 0.1, the
217 predecessor to OStatus.
218 - HTTP_Request2, a library for making HTTP requests.
220 A design goal of StatusNet is that the basic Web functionality should
221 work on even the most restrictive commercial hosting services.
222 However, additional functionality, such as receiving messages by
223 Jabber/GTalk, require that you be able to run long-running processes
224 on your account. In addition, posting by email or from SMS require
225 that you be able to install a mail filter in your mail server.
230 Installing the basic StatusNet Web component is relatively easy,
231 especially if you've previously installed PHP/MySQL packages.
233 1. Unpack the tarball you downloaded on your Web server. Usually a
234 command like this will work:
236 tar zxf statusnet-0.9.0.tar.gz
238 ...which will make a statusnet-0.9.0 subdirectory in your current
239 directory. (If you don't have shell access on your Web server, you
240 may have to unpack the tarball on your local computer and FTP the
241 files to the server.)
243 2. Move the tarball to a directory of your choosing in your Web root
244 directory. Usually something like this will work:
246 mv statusnet-0.9.0 /var/www/statusnet
248 This will make your StatusNet instance available in the statusnet path of
249 your server, like "http://example.net/statusnet". "microblog" or
250 "statusnet" might also be good path names. If you know how to
251 configure virtual hosts on your web server, you can try setting up
252 "http://micro.example.net/" or the like.
254 3. Make your target directory writeable by the Web server.
256 chmod a+w /var/www/statusnet/
258 On some systems, this will probably work:
260 chgrp www-data /var/www/statusnet/
261 chmod g+w /var/www/statusnet/
263 If your Web server runs as another user besides "www-data", try
264 that user's default group instead. As a last resort, you can create
265 a new group like "statusnet" and add the Web server's user to the group.
267 4. You should also take this moment to make your avatar, background, and
268 file subdirectories writeable by the Web server. An insecure way to do
271 chmod a+w /var/www/statusnet/avatar
272 chmod a+w /var/www/statusnet/background
273 chmod a+w /var/www/statusnet/file
275 You can also make the avatar, background, and file directories
276 writeable by the Web server group, as noted above.
278 5. Create a database to hold your microblog data. Something like this
281 mysqladmin -u "username" --password="password" create statusnet
283 Note that StatusNet must have its own database; you can't share the
284 database with another program. You can name it whatever you want,
287 (If you don't have shell access to your server, you may need to use
288 a tool like PHPAdmin to create a database. Check your hosting
289 service's documentation for how to create a new MySQL database.)
291 6. Create a new database account that StatusNet will use to access the
292 database. If you have shell access, this will probably work from the
295 GRANT ALL on statusnet.*
296 TO 'statusnetuser'@'localhost'
297 IDENTIFIED BY 'statusnetpassword';
299 You should change 'statusnetuser' and 'statusnetpassword' to your preferred new
300 username and password. You may want to test logging in to MySQL as
303 7. In a browser, navigate to the StatusNet install script; something like:
305 http://yourserver.example.com/statusnet/install.php
307 Enter the database connection information and your site name. The
308 install program will configure your site and install the initial,
309 almost-empty database.
311 8. You should now be able to navigate to your microblog's main directory
312 and see the "Public Timeline", which will be empty. If not, magic
313 has happened! You can now register a new user, post some notices,
314 edit your profile, etc. However, you may want to wait to do that stuff
315 if you think you can set up "fancy URLs" (see below), since some
316 URLs are stored in the database.
321 By default, StatusNet will use URLs that include the main PHP program's
322 name in them. For example, a user's home profile might be
325 http://example.org/statusnet/index.php/statusnet/fred
327 On certain systems that don't support this kind of syntax, they'll
330 http://example.org/statusnet/index.php?p=statusnet/fred
332 It's possible to configure the software so it looks like this instead:
334 http://example.org/statusnet/fred
336 These "fancy URLs" are more readable and memorable for users. To use
337 fancy URLs, you must either have Apache 2.x with .htaccess enabled and
338 mod_rewrite enabled, -OR- know how to configure "url redirection" in
341 1. Copy the htaccess.sample file to .htaccess in your StatusNet
342 directory. Note: if you have control of your server's httpd.conf or
343 similar configuration files, it can greatly improve performance to
344 import the .htaccess file into your conf file instead. If you're
345 not sure how to do it, you may save yourself a lot of headache by
346 just leaving the .htaccess file.
348 2. Change the "RewriteBase" in the new .htaccess file to be the URL path
349 to your StatusNet installation on your server. Typically this will
350 be the path to your StatusNet directory relative to your Web root.
352 3. Add or uncomment or change a line in your config.php file so it says:
354 $config['site']['fancy'] = true;
356 You should now be able to navigate to a "fancy" URL on your server,
359 http://example.net/statusnet/main/register
361 If you changed your HTTP server configuration, you may need to restart
364 If it doesn't work, double-check that AllowOverride for the StatusNet
365 directory is 'All' in your Apache configuration file. This is usually
366 /etc/httpd.conf, /etc/apache/httpd.conf, or (on Debian and Ubuntu)
367 /etc/apache2/sites-available/default. See the Apache documentation for
368 .htaccess files for more details:
370 http://httpd.apache.org/docs/2.2/howto/htaccess.html
372 Also, check that mod_rewrite is installed and enabled:
374 http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html
379 To use a Sphinx server to search users and notices, you'll need to
380 enable the SphinxSearch plugin. Add to your config.php:
382 addPlugin('SphinxSearch');
383 $config['sphinx']['server'] = 'searchhost.local';
385 You also need to install, compile and enable the sphinx pecl extension for
386 php on the client side, which itself depends on the sphinx development files.
388 See plugins/SphinxSearch/README for more details and server setup.
393 StatusNet supports a cheap-and-dirty system for sending update messages
394 to mobile phones and for receiving updates from the mobile. Instead of
395 sending through the SMS network itself, which is costly and requires
396 buy-in from the wireless carriers, it simply piggybacks on the email
397 gateways that many carriers provide to their customers. So, SMS
398 configuration is essentially email configuration.
400 Each user sends to a made-up email address, which they keep a secret.
401 Incoming email that is "From" the user's SMS email address, and "To"
402 the users' secret email address on the site's domain, will be
403 converted to a notice and stored in the DB.
405 For this to work, there *must* be a domain or sub-domain for which all
406 (or most) incoming email can pass through the incoming mail filter.
408 1. Run the SQL script carrier.sql in your StatusNet database. This will
411 mysql -u "statusnetuser" --password="statusnetpassword" statusnet < db/carrier.sql
413 This will populate your database with a list of wireless carriers
414 that support email SMS gateways.
416 2. Make sure the maildaemon.php file is executable:
418 chmod +x scripts/maildaemon.php
420 Note that "daemon" is kind of a misnomer here; the script is more
421 of a filter than a daemon.
423 2. Edit /etc/aliases on your mail server and add the following line:
425 *: /path/to/statusnet/scripts/maildaemon.php
427 3. Run whatever code you need to to update your aliases database. For
428 many mail servers (Postfix, Exim, Sendmail), this should work:
432 You may need to restart your mail server for the new database to
435 4. Set the following in your config.php file:
437 $config['mail']['domain'] = 'yourdomain.example.net';
439 At this point, post-by-email and post-by-SMS-gateway should work. Note
440 that if your mail server is on a different computer from your email
441 server, you'll need to have a full installation of StatusNet, a working
442 config.php, and access to the StatusNet database from the mail server.
447 XMPP (eXtended Message and Presence Protocol, <http://xmpp.org/>) is the
448 instant-messenger protocol that drives Jabber and GTalk IM. You can
449 distribute messages via XMPP using the system below; however, you
450 need to run the XMPP incoming daemon to allow incoming messages as
453 1. You may want to strongly consider setting up your own XMPP server.
454 Ejabberd, OpenFire, and JabberD are all Open Source servers.
455 Jabber, Inc. provides a high-performance commercial server.
457 2. You must register a Jabber ID (JID) with your new server. It helps
458 to choose a name like "update@example.com" or "notice" or something
459 similar. Alternately, your "update JID" can be registered on a
460 publicly-available XMPP service, like jabber.org or GTalk.
462 StatusNet will not register the JID with your chosen XMPP server;
463 you need to do this manually, with an XMPP client like Gajim,
464 Telepathy, or Pidgin.im.
466 3. Configure your site's XMPP variables, as described below in the
467 configuration section.
469 On a default installation, your site can broadcast messages using
470 XMPP. Users won't be able to post messages using XMPP unless you've
471 got the XMPP daemon running. See 'Queues and daemons' below for how
472 to set that up. Also, once you have a sizable number of users, sending
473 a lot of SMS, OMB, and XMPP messages whenever someone posts a message
474 can really slow down your site; it may cause posting to timeout.
476 NOTE: stream_select(), a crucial function for network programming, is
477 broken on PHP 5.2.x less than 5.2.6 on amd64-based servers. We don't
478 work around this bug in StatusNet; current recommendation is to move
479 off of amd64 to another server.
484 You can send *all* messages from your microblogging site to a
485 third-party service using XMPP. This can be useful for providing
486 search, indexing, bridging, or other cool services.
488 To configure a downstream site to receive your public stream, add
489 their "JID" (Jabber ID) to your config.php as follows:
491 $config['xmpp']['public'][] = 'downstream@example.net';
493 (Don't miss those square brackets at the end.) Note that your XMPP
494 broadcasting must be configured as mentioned above. Although you can
495 send out messages at "Web time", high-volume sites should strongly
496 consider setting up queues and daemons.
501 Some activities that StatusNet needs to do, like broadcast OMB, SMS,
502 and XMPP messages, can be 'queued' and done by off-line bots instead.
503 For this to work, you must be able to run long-running offline
504 processes, either on your main Web server or on another server you
505 control. (Your other server will still need all the above
506 prerequisites, with the exception of Apache.) Installing on a separate
507 server is probably a good idea for high-volume sites.
509 1. You'll need the "CLI" (command-line interface) version of PHP
510 installed on whatever server you use.
512 2. If you're using a separate server for queues, install StatusNet
513 somewhere on the server. You don't need to worry about the
514 .htaccess file, but make sure that your config.php file is close
515 to, or identical to, your Web server's version.
517 3. In your config.php files (both the Web server and the queues
518 server!), set the following variable:
520 $config['queue']['enabled'] = true;
522 You may also want to look at the 'daemon' section of this file for
523 more daemon options. Note that if you set the 'user' and/or 'group'
524 options, you'll need to create that user and/or group by hand.
525 They're not created automatically.
527 4. On the queues server, run the command scripts/startdaemons.sh. It
528 needs as a parameter the install path; if you run it from the
529 StatusNet dir, "." should suffice.
531 This will run the queue handlers:
533 * queuedaemon.php - polls for queued items for inbox processing and
534 pushing out to OMB, SMS, XMPP, etc.
535 * xmppdaemon.php - listens for new XMPP messages from users and stores
536 them as notices in the database; also pulls queued XMPP output from
537 queuedaemon.php to push out to clients.
539 These two daemons will automatically restart in most cases of failure
540 including memory leaks (if a memory_limit is set), but may still die
541 or behave oddly if they lose connections to the XMPP or queue servers.
543 It may be a good idea to use a daemon-monitoring service, like 'monit',
544 to check their status and keep them running.
546 All the daemons write their process IDs (pids) to /var/run/ by
547 default. This can be useful for starting, stopping, and monitoring the
550 Since version 0.8.0, it's now possible to use a STOMP server instead of
551 our kind of hacky home-grown DB-based queue solution. See the "queues"
552 config section below for how to configure to use STOMP. As of this
553 writing, the software has been tested with ActiveMQ.
558 There are two themes shipped with this version of StatusNet: "identica",
559 which is what the Identi.ca site uses, and "default", which is a good
560 basis for other sites.
562 As of right now, your ability to change the theme is site-wide; users
563 can't choose their own theme. Additionally, the only thing you can
564 change in the theme is CSS stylesheets and some image files; you can't
565 change the HTML output, like adding or removing menu items.
567 You can choose a theme using the $config['site']['theme'] element in
568 the config.php file. See below for details.
570 You can add your own theme by making a sub-directory of the 'theme'
571 subdirectory with the name of your theme. Each theme can have the
574 display.css: a CSS2 file for "default" styling for all browsers.
575 ie6.css: a CSS2 file for override styling for fixing up Internet
577 ie7.css: a CSS2 file for override styling for fixing up Internet
579 logo.png: a logo image for the site.
580 default-avatar-profile.png: a 96x96 pixel image to use as the avatar for
581 users who don't upload their own.
582 default-avatar-stream.png: Ditto, but 48x48. For streams of notices.
583 default-avatar-mini.png: Ditto ditto, but 24x24. For subscriptions
584 listing on profile pages.
586 You may want to start by copying the files from the default theme to
589 NOTE: the HTML generated by StatusNet changed *radically* between
590 version 0.6.x and 0.7.x. Older themes will need signification
591 modification to use the new output format.
596 Translations in StatusNet use the gettext system <http://www.gnu.org/software/gettext/>.
597 Theoretically, you can add your own sub-directory to the locale/
598 subdirectory to add a new language to your system. You'll need to
599 compile the ".po" files into ".mo" files, however.
601 Contributions of translation information to StatusNet are very easy:
602 you can use the Web interface at TranslateWiki.net to add one
603 or a few or lots of new translations -- or even new languages. You can
604 also download more up-to-date .po files there, if you so desire.
606 For info on helping with translations, see http://status.net/wiki/Translations
611 There is no built-in system for doing backups in StatusNet. You can make
612 backups of a working StatusNet system by backing up the database and
613 the Web directory. To backup the database use mysqldump <http://ur1.ca/7xo>
614 and to backup the Web directory, try tar.
619 The administrator can set the "private" flag for a site so that it's
620 not visible to non-logged-in users. This might be useful for
621 workgroups who want to share a microblogging site for project
622 management, but host it on a public server.
624 Note that this is an experimental feature; total privacy is not
625 guaranteed or ensured. Also, privacy is all-or-nothing for a site; you
626 can't have some accounts or notices private, and others public.
627 Finally, the interaction of private sites with OStatus is
628 undefined. Remote users won't be able to subscribe to users on a
629 private site, but users of the private site may be able to subscribe
630 to users on a remote site. (Or not... it's not well tested.) The
631 "proper behaviour" hasn't been defined here, so handle with care.
633 Access to file attachments can also be restricted to logged-in users only.
634 1. Add a directory outside the web root where your file uploads will be
635 stored. Usually a command like this will work:
637 mkdir /var/www/statusnet-files
639 2. Make the file uploads directory writeable by the web server. An
640 insecure way to do this is:
642 chmod a+x /var/www/statusnet-files
644 3. Tell StatusNet to use this directory for file uploads. Add a line
645 like this to your config.php:
647 $config['attachments']['dir'] = '/var/www/statusnet-files';
652 IMPORTANT NOTE: StatusNet 0.7.4 introduced a fix for some
653 incorrectly-stored international characters ("UTF-8"). For new
654 installations, it will now store non-ASCII characters correctly.
655 However, older installations will have the incorrect storage, and will
656 consequently show up "wrong" in browsers. See below for how to deal
659 If you've been using StatusNet 0.7, 0.6, 0.5 or lower, or if you've
660 been tracking the "git" version of the software, you will probably
661 want to upgrade and keep your existing data. There is no automated
662 upgrade procedure in StatusNet 0.9.0. Try these step-by-step
663 instructions; read to the end first before trying them.
665 0. Download StatusNet and set up all the prerequisites as if you were
667 1. Make backups of both your database and your Web directory. UNDER NO
668 CIRCUMSTANCES should you try to do an upgrade without a known-good
669 backup. You have been warned.
670 2. Shut down Web access to your site, either by turning off your Web
671 server or by redirecting all pages to a "sorry, under maintenance"
673 3. Shut down XMPP access to your site, typically by shutting down the
674 xmppdaemon.php process and all other daemons that you're running.
675 If you've got "monit" or "cron" automatically restarting your
676 daemons, make sure to turn that off, too.
677 4. Shut down SMS and email access to your site. The easy way to do
678 this is to comment out the line piping incoming email to your
679 maildaemon.php file, and running something like "newaliases".
680 5. Once all writing processes to your site are turned off, make a
681 final backup of the Web directory and database.
682 6. Move your StatusNet directory to a backup spot, like "statusnet.bak".
683 7. Unpack your StatusNet 0.9.0 tarball and move it to "statusnet" or
684 wherever your code used to be.
685 8. Copy the config.php file and avatar directory from your old
686 directory to your new directory.
687 9. Copy htaccess.sample to .htaccess in the new directory. Change the
688 RewriteBase to use the correct path.
689 10. Rebuild the database. (You can safely skip this step and go to #12
690 if you're upgrading from another 0.8.x version).
692 NOTE: this step is destructive and cannot be
693 reversed. YOU CAN EASILY DESTROY YOUR SITE WITH THIS STEP. Don't
694 do it without a known-good backup!
696 If your database is at version 0.7.4, you can run a special upgrade
699 mysql -u<rootuser> -p<rootpassword> <database> db/074to080.sql
701 Otherwise, go to your StatusNet directory and AFTER YOU MAKE A
702 BACKUP run the rebuilddb.sh script like this:
704 ./scripts/rebuilddb.sh rootuser rootpassword database db/statusnet.sql
706 Here, rootuser and rootpassword are the username and password for a
707 user who can drop and create databases as well as tables; typically
708 that's _not_ the user StatusNet runs as. Note that rebuilddb.sh drops
709 your database and rebuilds it; if there is an error you have no
710 database. Make sure you have a backup.
711 For PostgreSQL databases there is an equivalent, rebuilddb_psql.sh,
712 which operates slightly differently. Read the documentation in that
713 script before running it.
714 11. Use mysql or psql client to log into your database and make sure that
715 the notice, user, profile, subscription etc. tables are non-empty.
716 12. Turn back on the Web server, and check that things still work.
717 13. Turn back on XMPP bots and email maildaemon. Note that the XMPP
718 bots have changed since version 0.5; see above for details.
720 If you're upgrading from very old versions, you may want to look at
721 the fixup_* scripts in the scripts directories. These will store some
722 precooked data in the DB. All upgraders should check out the inboxes
725 NOTE: the database definition file, laconica.ini, has been renamed to
726 statusnet.ini (since this is the recommended database name). If you
727 have a line in your config.php pointing to the old name, you'll need
733 Notice inboxes are now required. If you don't have inboxes enabled,
734 StatusNet will no longer run.
739 StatusNet 0.7.4 introduced a fix for some incorrectly-stored
740 international characters ("UTF-8"). This fix is not
741 backwards-compatible; installations from before 0.7.4 will show
742 non-ASCII characters of old notices incorrectly. This section explains
745 0. You can disable the new behaviour by setting the 'db''utf8' config
746 option to "false". You should only do this until you're ready to
747 convert your DB to the new format.
748 1. When you're ready to convert, you can run the fixup_utf8.php script
749 in the scripts/ subdirectory. If you've had the "new behaviour"
750 enabled (probably a good idea), you can give the ID of the first
751 "new" notice as a parameter, and only notices before that one will
752 be converted. Notices are converted in reverse chronological order,
753 so the most recent (and visible) ones will be converted first. The
754 script should work whether or not you have the 'db''utf8' config
756 2. When you're ready, set $config['db']['utf8'] to true, so that
757 new notices will be stored correctly.
759 Configuration options
760 =====================
762 The main configuration file for StatusNet (excepting configurations for
763 dependency software) is config.php in your StatusNet directory. If you
764 edit any other file in the directory, like lib/common.php (where most
765 of the defaults are defined), you will lose your configuration options
766 in any upgrade, and you will wish that you had been more careful.
768 Starting with version 0.7.1, you can put config files in the
769 /etc/statusnet/ directory on your server, if it exists. Config files
770 will be included in this order:
772 * /etc/statusnet/statusnet.php - server-wide config
773 * /etc/statusnet/<servername>.php - for a virtual host
774 * /etc/statusnet/<servername>_<pathname>.php - for a path
775 * INSTALLDIR/config.php - for a particular implementation
777 Almost all configuration options are made through a two-dimensional
778 associative array, cleverly named $config. A typical configuration
781 $config['section']['option'] = value;
783 For brevity, the following documentation describes each section and
789 This section is a catch-all for site-wide variables.
791 name: the name of your site, like 'YourCompany Microblog'.
792 server: the server part of your site's URLs, like 'example.net'.
793 path: The path part of your site's URLs, like 'statusnet' or ''
795 fancy: whether or not your site uses fancy URLs (see Fancy URLs
796 section above). Default is false.
797 logfile: full path to a file for StatusNet to save logging
798 information to. You may want to use this if you don't have
800 logdebug: whether to log additional debug info like backtraces on
801 hard errors. Default false.
802 locale_path: full path to the directory for locale data. Unless you
803 store all your locale data in one place, you probably
804 don't need to use this.
805 language: default language for your site. Defaults to US English.
806 Note that this is overridden if a user is logged in and has
807 selected a different language. It is also overridden if the
808 user is NOT logged in, but their browser requests a different
809 langauge. Since pretty much everybody's browser requests a
810 language, that means that changing this setting has little or
811 no effect in practice.
812 languages: A list of languages supported on your site. Typically you'd
813 only change this if you wanted to disable support for one
815 "unset($config['site']['languages']['de'])" will disable
817 theme: Theme for your site (see Theme section). Two themes are
818 provided by default: 'default' and 'stoica' (the one used by
819 Identi.ca). It's appreciated if you don't use the 'stoica' theme
820 except as the basis for your own.
821 email: contact email address for your site. By default, it's extracted
822 from your Web server environment; you may want to customize it.
823 broughtbyurl: name of an organization or individual who provides the
824 service. Each page will include a link to this name in the
825 footer. A good way to link to the blog, forum, wiki,
826 corporate portal, or whoever is making the service available.
827 broughtby: text used for the "brought by" link.
828 timezone: default timezone for message display. Users can set their
829 own time zone. Defaults to 'UTC', which is a pretty good default.
830 closed: If set to 'true', will disallow registration on your site.
831 This is a cheap way to restrict accounts to only one
832 individual or group; just register the accounts you want on
833 the service, *then* set this variable to 'true'.
834 inviteonly: If set to 'true', will only allow registration if the user
835 was invited by an existing user.
836 private: If set to 'true', anonymous users will be redirected to the
837 'login' page. Also, API methods that normally require no
838 authentication will require it. Note that this does not turn
839 off registration; use 'closed' or 'inviteonly' for the
841 notice: A plain string that will appear on every page. A good place
842 to put introductory information about your service, or info about
843 upgrades and outages, or other community info. Any HTML will
845 logo: URL of an image file to use as the logo for the site. Overrides
846 the logo in the theme, if any.
847 ssl: Whether to use SSL and https:// URLs for some or all pages.
848 Possible values are 'always' (use it for all pages), 'never'
849 (don't use it for any pages), or 'sometimes' (use it for
850 sensitive pages that include passwords like login and registration,
851 but not for regular pages). Default to 'never'.
852 sslserver: use an alternate server name for SSL URLs, like
853 'secure.example.org'. You should be careful to set cookie
854 parameters correctly so that both the SSL server and the
855 "normal" server can access the session cookie and
856 preferably other cookies as well.
857 shorturllength: Length of URL at which URLs in a message exceeding 140
858 characters will be sent to the user's chosen
860 dupelimit: minimum time allowed for one person to say the same thing
861 twice. Default 60s. Anything lower is considered a user
863 textlimit: default max size for texts in the site. Defaults to 140.
864 0 means no limit. Can be fine-tuned for notices, messages,
865 profile bios and group descriptions.
870 This section is a reference to the configuration options for
871 DB_DataObject (see <http://ur1.ca/7xp>). The ones that you may want to
872 set are listed below for clarity.
874 database: a DSN (Data Source Name) for your StatusNet database. This is
875 in the format 'protocol://username:password@hostname/databasename',
876 where 'protocol' is 'mysql' or 'mysqli' (or possibly 'postgresql', if you
877 really know what you're doing), 'username' is the username,
878 'password' is the password, and etc.
879 ini_yourdbname: if your database is not named 'statusnet', you'll need
880 to set this to point to the location of the
881 statusnet.ini file. Note that the real name of your database
882 should go in there, not literally 'yourdbname'.
883 db_driver: You can try changing this to 'MDB2' to use the other driver
884 type for DB_DataObject, but note that it breaks the OpenID
885 libraries, which only support PEAR::DB.
886 debug: On a database error, you may get a message saying to set this
887 value to 5 to see debug messages in the browser. This breaks
888 just about all pages, and will also expose the username and
890 quote_identifiers: Set this to true if you're using postgresql.
891 type: either 'mysql' or 'postgresql' (used for some bits of
892 database-type-specific SQL in the code). Defaults to mysql.
893 mirror: you can set this to an array of DSNs, like the above
894 'database' value. If it's set, certain read-only actions will
895 use a random value out of this array for the database, rather
896 than the one in 'database' (actually, 'database' is overwritten).
897 You can offload a busy DB server by setting up MySQL replication
898 and adding the slaves to this array. Note that if you want some
899 requests to go to the 'database' (master) server, you'll need
900 to include it in this array, too.
901 utf8: whether to talk to the database in UTF-8 mode. This is the default
902 with new installations, but older sites may want to turn it off
903 until they get their databases fixed up. See "UTF-8 database"
905 schemacheck: when to let plugins check the database schema to add
906 tables or update them. Values can be 'runtime' (default)
907 or 'script'. 'runtime' can be costly (plugins check the
908 schema on every hit, adding potentially several db
909 queries, some quite long), but not everyone knows how to
910 run a script. If you can, set this to 'script' and run
911 scripts/checkschema.php whenever you install or upgrade a
917 By default, StatusNet sites log error messages to the syslog facility.
918 (You can override this using the 'logfile' parameter described above).
920 appname: The name that StatusNet uses to log messages. By default it's
921 "statusnet", but if you have more than one installation on the
922 server, you may want to change the name for each instance so
923 you can track log messages more easily.
924 priority: level to log at. Currently ignored.
925 facility: what syslog facility to used. Defaults to LOG_USER, only
926 reset if you know what syslog is and have a good reason
932 You can configure the software to queue time-consuming tasks, like
933 sending out SMS email or XMPP messages, for off-line processing. See
934 'Queues and daemons' above for how to set this up.
936 enabled: Whether to uses queues. Defaults to false.
937 subsystem: Which kind of queueserver to use. Values include "db" for
938 our hacked-together database queuing (no other server
939 required) and "stomp" for a stomp server.
940 stomp_server: "broker URI" for stomp server. Something like
941 "tcp://hostname:61613". More complicated ones are
942 possible; see your stomp server's documentation for
944 queue_basename: a root name to use for queues (stomp only). Typically
945 something like '/queue/sitename/' makes sense.
946 stomp_username: username for connecting to the stomp server; defaults
948 stomp_password: password for connecting to the stomp server; defaults
953 The default license to use for your users notices. The default is the
954 Creative Commons Attribution 3.0 license, which is probably the right
955 choice for any public site. Note that some other servers will not
956 accept notices if you apply a stricter license than this.
958 type: one of 'cc' (for Creative Commons licenses), 'allrightsreserved'
959 (default copyright), or 'private' (for private and confidential
961 owner: for 'allrightsreserved' or 'private', an assigned copyright
962 holder (for example, an employer for a private site). If
963 not specified, will be attributed to 'contributors'.
964 url: URL of the license, used for links.
965 title: Title for the license, like 'Creative Commons Attribution 3.0'.
966 image: A button shown on each page for the license.
971 This is for configuring out-going email. We use PEAR's Mail module,
972 see: http://pear.php.net/manual/en/package.mail.mail.factory.php
974 backend: the backend to use for mail, one of 'mail', 'sendmail', and
975 'smtp'. Defaults to PEAR's default, 'mail'.
976 params: if the mail backend requires any parameters, you can provide
977 them in an associative array.
982 This is for configuring nicknames in the service.
984 blacklist: an array of strings for usernames that may not be
985 registered. A default array exists for strings that are
986 used by StatusNet (e.g. 'doc', 'main', 'avatar', 'theme')
987 but you may want to add others if you have other software
988 installed in a subdirectory of StatusNet or if you just
989 don't want certain words used as usernames.
990 featured: an array of nicknames of 'featured' users of the site.
991 Can be useful to draw attention to well-known users, or
992 interesting people, or whatever.
997 For configuring avatar access.
999 dir: Directory to look for avatar files and to put them into.
1000 Defaults to avatar subdirectory of install directory; if
1001 you change it, make sure to change path, too.
1002 path: Path to avatars. Defaults to path for avatar subdirectory,
1003 but you can change it if you wish. Note that this will
1004 be included with the avatar server, too.
1005 server: If set, defines another server where avatars are stored in the
1006 root directory. Note that the 'avatar' subdir still has to be
1007 writeable. You'd typically use this to split HTTP requests on
1008 the client to speed up page loading, either with another
1009 virtual server or with an NFS or SAMBA share. Clients
1010 typically only make 2 connections to a single server at a
1011 time <http://ur1.ca/6ih>, so this can parallelize the job.
1013 ssl: Whether to access avatars using HTTPS. Defaults to null, meaning
1014 to guess based on site-wide SSL settings.
1019 For configuring the public stream.
1021 localonly: If set to true, only messages posted by users of this
1022 service (rather than other services, filtered through OMB)
1023 are shown in the public stream. Default true.
1024 blacklist: An array of IDs of users to hide from the public stream.
1025 Useful if you have someone making excessive Twitterfeed posts
1026 to the site, other kinds of automated posts, testing bots, etc.
1027 autosource: Sources of notices that are from automatic posters, and thus
1028 should be kept off the public timeline. Default empty.
1033 server: Like avatars, you can speed up page loading by pointing the
1034 theme file lookup to another server (virtual or real).
1035 Defaults to NULL, meaning to use the site server.
1036 dir: Directory where theme files are stored. Used to determine
1037 whether to show parts of a theme file. Defaults to the theme
1038 subdirectory of the install directory.
1039 path: Path part of theme URLs, before the theme name. Relative to the
1040 theme server. It may make sense to change this path when upgrading,
1041 (using version numbers as the path) to make sure that all files are
1042 reloaded by caching clients or proxies. Defaults to null,
1043 which means to use the site path + '/theme'.
1044 ssl: Whether to use SSL for theme elements. Default is null, which means
1045 guess based on site SSL settings.
1050 server: You can speed up page loading by pointing the
1051 theme file lookup to another server (virtual or real).
1052 Defaults to NULL, meaning to use the site server.
1053 path: Path part of Javascript URLs. Defaults to null,
1054 which means to use the site path + '/js/'.
1055 ssl: Whether to use SSL for JavaScript files. Default is null, which means
1056 guess based on site SSL settings.
1061 For configuring the XMPP sub-system.
1063 enabled: Whether to accept and send messages by XMPP. Default false.
1064 server: server part of XMPP ID for update user.
1065 port: connection port for clients. Default 5222, which you probably
1066 shouldn't need to change.
1067 user: username for the client connection. Users will receive messages
1068 from 'user'@'server'.
1069 resource: a unique identifier for the connection to the server. This
1070 is actually used as a prefix for each XMPP component in the system.
1071 password: password for the user account.
1072 host: some XMPP domains are served by machines with a different
1073 hostname. (For example, @gmail.com GTalk users connect to
1074 talk.google.com). Set this to the correct hostname if that's the
1075 case with your server.
1076 encryption: Whether to encrypt the connection between StatusNet and the
1077 XMPP server. Defaults to true, but you can get
1078 considerably better performance turning it off if you're
1079 connecting to a server on the same machine or on a
1081 debug: if turned on, this will make the XMPP library blurt out all of
1082 the incoming and outgoing messages as XML stanzas. Use as a
1083 last resort, and never turn it on if you don't have queues
1084 enabled, since it will spit out sensitive data to the browser.
1085 public: an array of JIDs to send _all_ notices to. This is useful for
1086 participating in third-party search and archiving services.
1091 For configuring invites.
1093 enabled: Whether to allow users to send invites. Default true.
1098 Miscellaneous tagging stuff.
1100 dropoff: Decay factor for tag listing, in seconds.
1101 Defaults to exponential decay over ten days; you can twiddle
1102 with it to try and get better results for your site.
1107 Settings for the "popular" section of the site.
1109 dropoff: Decay factor for popularity listing, in seconds.
1110 Defaults to exponential decay over ten days; you can twiddle
1111 with it to try and get better results for your site.
1116 For daemon processes.
1118 piddir: directory that daemon processes should write their PID file
1119 (process ID) to. Defaults to /var/run/, which is where this
1120 stuff should usually go on Unix-ish systems.
1121 user: If set, the daemons will try to change their effective user ID
1122 to this user before running. Probably a good idea, especially if
1123 you start the daemons as root. Note: user name, like 'daemon',
1125 group: If set, the daemons will try to change their effective group ID
1126 to this named group. Again, a name, not a numerical ID.
1131 You can get a significant boost in performance by caching some
1132 database data in memcached <http://www.danga.com/memcached/>.
1134 enabled: Set to true to enable. Default false.
1135 server: a string with the hostname of the memcached server. Can also
1136 be an array of hostnames, if you've got more than one server.
1137 base: memcached uses key-value pairs to store data. We build long,
1138 funny-looking keys to make sure we don't have any conflicts. The
1139 base of the key is usually a simplified version of the site name
1140 (like "Identi.ca" => "identica"), but you can overwrite this if
1141 you need to. You can safely ignore it if you only have one
1142 StatusNet site using your memcached server.
1143 port: Port to connect to; defaults to 11211.
1150 enabled: Whether to enable post-by-email. Defaults to true. You will
1151 also need to set up maildaemon.php.
1156 For SMS integration.
1158 enabled: Whether to enable SMS integration. Defaults to true. Queues
1159 should also be enabled.
1164 A catch-all for integration with other systems.
1166 taguri: base for tag:// URIs. Defaults to site-server + ',2009'.
1173 enabled: No longer used. If you set this to something other than true,
1174 StatusNet will no longer run.
1179 For notice-posting throttles.
1181 enabled: Whether to throttle posting. Defaults to false.
1182 count: Each user can make this many posts in 'timespan' seconds. So, if count
1183 is 100 and timespan is 3600, then there can be only 100 posts
1184 from a user every hour.
1185 timespan: see 'count'.
1192 banned: an array of usernames and/or profile IDs of 'banned' profiles.
1193 The site will reject any notices by these users -- they will
1194 not be accepted at all. (Compare with blacklisted users above,
1195 whose posts just won't show up in the public stream.)
1196 biolimit: max character length of bio; 0 means no limit; null means to use
1197 the site text limit default.
1202 Options with new users.
1204 default: nickname of a user account to automatically subscribe new
1205 users to. Typically this would be system account for e.g.
1206 service updates or announcements. Users are able to unsub
1207 if they want. Default is null; no auto subscribe.
1208 welcome: nickname of a user account that sends welcome messages to new
1209 users. Can be the same as 'default' account, although on
1210 busy servers it may be a good idea to keep that one just for
1211 'urgent' messages. Default is null; no message.
1213 If either of these special user accounts are specified, the users should
1214 be created before the configuration is updated.
1219 The software will, by default, send statistical snapshots about the
1220 local installation to a stats server on the status.net Web site. This
1221 data is used by the developers to prioritize development decisions. No
1222 identifying data about users or organizations is collected. The data
1223 is available to the public for review. Participating in this survey
1224 helps StatusNet developers take your needs into account when updating
1227 run: string indicating when to run the statistics. Values can be 'web'
1228 (run occasionally at Web time), 'cron' (run from a cron script),
1229 or 'never' (don't ever run). If you set it to 'cron', remember to
1230 schedule the script to run on a regular basis.
1231 frequency: if run value is 'web', how often to report statistics.
1232 Measured in Web hits; depends on how active your site is.
1233 Default is 10000 -- that is, one report every 10000 Web hits,
1235 reporturl: URL to post statistics to. Defaults to StatusNet developers'
1236 report system, but if they go evil or disappear you may
1237 need to update this to another value. Note: if you
1238 don't want to report stats, it's much better to
1239 set 'run' to 'never' than to set this value to something
1245 The software lets users upload files with their notices. You can configure
1246 the types of accepted files by mime types and a trio of quota options:
1247 per file, per user (total), per user per month.
1249 We suggest the use of the pecl file_info extension to handle mime type
1252 supported: an array of mime types you accept to store and distribute,
1253 like 'image/gif', 'video/mpeg', 'audio/mpeg', etc. Make sure you
1254 setup your server to properly recognize the types you want to
1256 uploads: false to disable uploading files with notices (true by default).
1257 filecommand: The required MIME_Type library may need to use the 'file'
1258 command. It tries the one in the Web server's path, but if
1259 you're having problems with uploads, try setting this to the
1260 correct value. Note: 'file' must accept '-b' and '-i' options.
1262 For quotas, be sure you've set the upload_max_filesize and post_max_size
1263 in php.ini to be large enough to handle your upload. In httpd.conf
1264 (if you're using apache), check that the LimitRequestBody directive isn't
1265 set too low (it's optional, so it may not be there at all).
1267 file_quota: maximum size for a single file upload in bytes. A user can send
1268 any amount of notices with attachments as long as each attachment
1269 is smaller than file_quota.
1270 user_quota: total size in bytes a user can store on this server. Each user
1271 can store any number of files as long as their total size does
1272 not exceed the user_quota.
1273 monthly_quota: total size permitted in the current month. This is the total
1274 size in bytes that a user can upload each month.
1275 dir: directory accessible to the Web process where uploads should go.
1276 Defaults to the 'file' subdirectory of the install directory, which
1277 should be writeable by the Web user.
1278 server: server name to use when creating URLs for uploaded files.
1279 Defaults to null, meaning to use the default Web server. Using
1280 a virtual server here can speed up Web performance.
1281 path: URL path, relative to the server, to find files. Defaults to
1282 main path + '/file/'.
1283 ssl: whether to use HTTPS for file URLs. Defaults to null, meaning to
1284 guess based on other SSL settings.
1285 filecommand: command to use for determining the type of a file. May be
1286 skipped if fileinfo extension is installed. Defaults to
1292 Options for group functionality.
1294 maxaliases: maximum number of aliases a group can have. Default 3. Set
1295 to 0 or less to prevent aliases in a group.
1296 desclimit: maximum number of characters to allow in group descriptions.
1297 null (default) means to use the site-wide text limits. 0
1303 oEmbed endpoint for multimedia attachments (links in posts).
1305 endpoint: oohembed endpoint using http://oohembed.com/ software.
1310 Some stuff for search.
1312 type: type of search. Ignored if PostgreSQL or Sphinx are enabled. Can either
1313 be 'fulltext' (default) or 'like'. The former is faster and more efficient
1314 but requires the lame old MyISAM engine for MySQL. The latter
1315 will work with InnoDB but could be miserably slow on large
1316 systems. We'll probably add another type sometime in the future,
1317 with our own indexing system (maybe like MediaWiki's).
1324 handle: boolean. Whether we should register our own PHP session-handling
1325 code (using the database and memcache if enabled). Defaults to false.
1326 Setting this to true makes some sense on large or multi-server
1327 sites, but it probably won't hurt for smaller ones, either.
1328 debug: whether to output debugging info for session storage. Can help
1329 with weird session bugs, sometimes. Default false.
1334 Users can upload backgrounds for their pages; this section defines
1337 server: the server to use for background. Using a separate (even
1338 virtual) server for this can speed up load times. Default is
1339 null; same as site server.
1340 dir: directory to write backgrounds too. Default is '/background/'
1341 subdir of install dir.
1342 path: path to backgrounds. Default is sub-path of install path; note
1343 that you may need to change this if you change site-path too.
1344 ssl: Whether or not to use HTTPS for background files. Defaults to
1345 null, meaning to guess from site-wide SSL settings.
1350 Using the "XML-RPC Ping" method initiated by weblogs.com, the site can
1351 notify third-party servers of updates.
1353 notify: an array of URLs for ping endpoints. Default is the empty
1354 array (no notification).
1359 Default design (colors and background) for the site. Actual appearance
1360 depends on the theme. Null values mean to use the theme defaults.
1362 backgroundcolor: Hex color of the site background.
1363 contentcolor: Hex color of the content area background.
1364 sidebarcolor: Hex color of the sidebar background.
1365 textcolor: Hex color of all non-link text.
1366 linkcolor: Hex color of all links.
1367 backgroundimage: Image to use for the background.
1368 disposition: Flags for whether or not to tile the background image.
1373 Configuration options specific to notices.
1375 contentlimit: max length of the plain-text content of a notice.
1376 Default is null, meaning to use the site-wide text limit.
1382 Configuration options specific to messages.
1384 contentlimit: max length of the plain-text content of a message.
1385 Default is null, meaning to use the site-wide text limit.
1391 Configuration options for the login command.
1393 disabled: whether to enable this command. If enabled, users who send
1394 the text 'login' to the site through any channel will
1395 receive a link to login to the site automatically in return.
1396 Possibly useful for users who primarily use an XMPP or SMS
1397 interface and can't be bothered to remember their site
1398 password. Note that the security implications of this are
1399 pretty serious and have not been thoroughly tested. You
1400 should enable it only after you've convinced yourself that
1401 it is safe. Default is 'false'.
1406 If an installation has only one user, this can simplify a lot of the
1407 interface. It also makes the user's profile the root URL.
1409 enabled: Whether to run in "single user mode". Default false.
1410 nickname: nickname of the single user.
1415 We put out a default robots.txt file to guide the processing of
1416 Web crawlers. See http://www.robotstxt.org/ for more information
1417 on the format of this file.
1419 crawldelay: if non-empty, this value is provided as the Crawl-Delay:
1420 for the robots.txt file. see http://ur1.ca/l5a0
1421 for more information. Default is zero, no explicit delay.
1422 disallow: Array of (virtual) directories to disallow. Default is 'main',
1423 'search', 'message', 'settings', 'admin'. Ignored when site
1424 is private, in which case the entire site ('/') is disallowed.
1429 Beginning with the 0.7.x branch, StatusNet has supported a simple but
1430 powerful plugin architecture. Important events in the code are named,
1431 like 'StartNoticeSave', and other software can register interest
1432 in those events. When the events happen, the other software is called
1433 and has a choice of accepting or rejecting the events.
1435 In the simplest case, you can add a function to config.php and use the
1436 Event::addHandler() function to hook an event:
1438 function AddGoogleLink($action)
1440 $action->menuItem('http://www.google.com/', _('Google'), _('Search engine'));
1444 Event::addHandler('EndPrimaryNav', 'AddGoogleLink');
1446 This adds a menu item to the end of the main navigation menu. You can
1447 see the list of existing events, and parameters that handlers must
1448 implement, in EVENTS.txt.
1450 The Plugin class in lib/plugin.php makes it easier to write more
1451 complex plugins. Sub-classes can just create methods named
1452 'onEventName', where 'EventName' is the name of the event (case
1453 matters!). These methods will be automatically registered as event
1454 handlers by the Plugin constructor (which you must call from your own
1455 class's constructor).
1457 Several example plugins are included in the plugins/ directory. You
1458 can enable a plugin with the following line in config.php:
1460 addPlugin('Example', array('param1' => 'value1',
1461 'param2' => 'value2'));
1463 This will look for and load files named 'ExamplePlugin.php' or
1464 'Example/ExamplePlugin.php' either in the plugins/ directory (for
1465 plugins that ship with StatusNet) or in the local/ directory (for
1466 plugins you write yourself or that you get from somewhere else) or
1469 Plugins are documented in their own directories.
1474 The primary output for StatusNet is syslog, unless you configured a
1475 separate logfile. This is probably the first place to look if you're
1476 getting weird behaviour from StatusNet.
1478 If you're tracking the unstable version of StatusNet in the git
1479 repository (see below), and you get a compilation error ("unexpected
1480 T_STRING") in the browser, check to see that you don't have any
1481 conflicts in your code.
1483 If you upgraded to StatusNet 0.9.0 without reading the "Notice
1484 inboxes" section above, and all your users' 'Personal' tabs are empty,
1485 read the "Notice inboxes" section above.
1490 These are some myths you may see on the Web about StatusNet.
1491 Documentation from the core team about StatusNet has been pretty
1492 sparse, so some backtracking and guesswork resulted in some incorrect
1495 - "Set $config['db']['debug'] = 5 to debug the database." This is an
1496 extremely bad idea. It's a tool built into DB_DataObject that will
1497 emit oodles of print lines directly to the browser of your users.
1498 Among these lines will be your database username and password. Do
1499 not enable this option on a production Web site for any reason.
1501 - "Edit dataobject.ini with the following settings..." dataobject.ini
1502 is a development file for the DB_DataObject framework and is not
1503 used by the running software. It was removed from the StatusNet
1504 distribution because its presence was confusing. Do not bother
1505 configuring dataobject.ini, and do not put your database username
1506 and password into the file on a production Web server; unscrupulous
1507 persons may try to read it to get your passwords.
1512 If you're adventurous or impatient, you may want to install the
1513 development version of StatusNet. To get it, use the git version
1514 control tool <http://git-scm.com/> like so:
1516 git clone git@gitorious.org:statusnet/mainline.git
1518 This is the version of the software that runs on Identi.ca and the
1519 status.net hosted service. Using it is a mixed bag. On the positive
1520 side, it usually includes the latest security and bug fix patches. On
1521 the downside, it may also include changes that require admin
1522 intervention (like running a script or even raw SQL!) that may not be
1523 documented yet. It may be a good idea to test this version before
1524 installing it on your production machines.
1526 To keep it up-to-date, use 'git pull'. Watch for conflicts!
1531 There are several ways to get more information about StatusNet.
1533 * There is a mailing list for StatusNet developers and admins at
1534 http://mail.status.net/mailman/listinfo/statusnet-dev
1535 * The #statusnet IRC channel on freenode.net <http://www.freenode.net/>.
1536 * The StatusNet wiki, http://status.net/wiki/
1537 * The StatusNet blog, http://status.net/blog/
1538 * The StatusNet status update, <http://status.status.net/> (!)
1543 * Microblogging messages to http://support.status.net/ are very welcome.
1544 * The microblogging group http://identi.ca/group/statusnet is a good
1545 place to discuss the software.
1546 * StatusNet has a bug tracker for any defects you may find, or ideas for
1547 making things better. http://status.net/bugs
1552 The following is an incomplete list of developers who've worked on
1553 StatusNet. Apologies for any oversight; please let evan@status.net know
1554 if anyone's been overlooked in error.
1556 * Evan Prodromou, founder and lead developer, StatusNet, Inc.
1557 * Zach Copley, StatusNet, Inc.
1558 * Earle Martin, StatusNet, Inc.
1559 * Marie-Claude Doyon, designer, StatusNet, Inc.
1560 * Sarven Capadisli, StatusNet, Inc.
1561 * Robin Millette, StatusNet, Inc.
1572 * Tryggvi Björgvinsson
1576 * Ken Sheppardson (Trac server, man-about-town)
1577 * Tiago 'gouki' Faria (i18n manager)
1579 * Leslie Michael Orchard
1583 * Tobias Diekershoff
1595 Thanks also to the developers of our upstream library code and to the
1596 thousands of people who have tried out Identi.ca, installed StatusNet,
1597 told their friends, and built the Open Microblogging network to what