GNUsocial
/
gnu-social
4
0
Fork 1
Code Issues Releases Wiki Activity

some more editorial on README

This commit is contained in:
Evan Prodromou 2010-03-04 13:34:05 -05:00
parent ffbf821809
commit b98fcffcd2
1 changed files with 15 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

27
README
View File

@ -621,14 +621,10 @@ not visible to non-logged-in users. This might be useful for
workgroups who want to share a microblogging site for project workgroups who want to share a microblogging site for project
management, but host it on a public server. management, but host it on a public server.
Note that this is an experimental feature; total privacy is not Total privacy is not guaranteed or ensured. Also, privacy is
guaranteed or ensured. Also, privacy is all-or-nothing for a site; you all-or-nothing for a site; you can't have some accounts or notices
can't have some accounts or notices private, and others public. private, and others public. The interaction of private sites
Finally, the interaction of private sites with OStatus is with OStatus is undefined.
undefined. Remote users won't be able to subscribe to users on a
private site, but users of the private site may be able to subscribe
to users on a remote site. (Or not... it's not well tested.) The
"proper behaviour" hasn't been defined here, so handle with care.
Access to file attachments can also be restricted to logged-in users only. Access to file attachments can also be restricted to logged-in users only.
1. Add a directory outside the web root where your file uploads will be 1. Add a directory outside the web root where your file uploads will be
@ -693,10 +689,10 @@ instructions; read to the end first before trying them.
reversed. YOU CAN EASILY DESTROY YOUR SITE WITH THIS STEP. Don't reversed. YOU CAN EASILY DESTROY YOUR SITE WITH THIS STEP. Don't
do it without a known-good backup! do it without a known-good backup!
If your database is at version 0.7.4, you can run a special upgrade If your database is at version 0.8.0 or above, you can run a
script: special upgrade script:
mysql -u<rootuser> -p<rootpassword> <database> db/074to080.sql mysql -u<rootuser> -p<rootpassword> <database> db/08to09.sql
Otherwise, go to your StatusNet directory and AFTER YOU MAKE A Otherwise, go to your StatusNet directory and AFTER YOU MAKE A
BACKUP run the rebuilddb.sh script like this: BACKUP run the rebuilddb.sh script like this:
@ -761,10 +757,17 @@ Configuration options
The main configuration file for StatusNet (excepting configurations for The main configuration file for StatusNet (excepting configurations for
dependency software) is config.php in your StatusNet directory. If you dependency software) is config.php in your StatusNet directory. If you
edit any other file in the directory, like lib/common.php (where most edit any other file in the directory, like lib/default.php (where most
of the defaults are defined), you will lose your configuration options of the defaults are defined), you will lose your configuration options
in any upgrade, and you will wish that you had been more careful. in any upgrade, and you will wish that you had been more careful.
Starting with version 0.9.0, a Web based configuration panel has been
added to StatusNet. The preferred method for changing config options is
to use this panel.
A command-line script, setconfig.php, can be used to set individual
configuration options. It's in the scripts/ directory.
Starting with version 0.7.1, you can put config files in the Starting with version 0.7.1, you can put config files in the
/etc/statusnet/ directory on your server, if it exists. Config files /etc/statusnet/ directory on your server, if it exists. Config files
will be included in this order: will be included in this order: