Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 16
- Log:
Configured for temporary /rails/typo location on Alpha. Updated
several layouts for RISC OS Open Limited site style. Now produces
proper "Not found" page in redirect_controller.rb. Updates to
database schema from Typo SVN (small change in the way tables are
defined, but same tables end up being defined). Set location of
SendMail in vendor/rails/actionmailer/lib/action_mailer/base.rb.
- Author:
- adh
- Date:
- Sun Jul 23 10:51:56 +0100 2006
- Size:
- 3538 Bytes
| 1 | What is it? |
| 2 | =========== |
| 3 | |
| 4 | Typo is a weblog system written in Ruby using Ruby on Rails. Weblogs are cool, |
| 5 | weblogs are "in" and everyone who writes code has an different opinion on how |
| 6 | a weblog should be written. Typo is our take on it. Typo is designed to be |
| 7 | usable by programmers and non-programmers, while being easy for programmers to |
| 8 | extend. |
| 9 | |
| 10 | Requirements |
| 11 | ============ |
| 12 | |
| 13 | Currently you need all of those things to get typo to run: |
| 14 | |
| 15 | * Ruby -v of 1.8.2 (25-05-2004) or 1.8.3 |
| 16 | * Rails 0.14.2 (or possibly 0.14.3) |
| 17 | * A database. Typo supports MySQL, PostgreSQL, and SQLite. |
| 18 | * Ruby drivers for your database. |
| 19 | * For best performance, you should have a web server running either |
| 20 | Apache or Lighttpd along with FastCGI, although these aren't |
| 21 | strictly required--you can use Ruby's built-in web server for |
| 22 | low-volume testing. |
| 23 | |
| 24 | Installation |
| 25 | ============ |
| 26 | |
| 27 | Unpack the tgz or zip in some directory. |
| 28 | |
| 29 | Decide which database to use. We support Sqlite, MySQL, and Postgres, |
| 30 | but Sqlite doesn't have full support for database migrations in Rails |
| 31 | 0.13.1. |
| 32 | |
| 33 | * Create a database for typo. You can find schemas in the db/ folder. |
| 34 | * Create config/database.yml using database.yml.example to reflect your |
| 35 | newly created database configuration |
| 36 | * Run script/server -e production and see if it works |
| 37 | * Point your browser to http://your.domain.com:3000/ and follow the |
| 38 | install process |
| 39 | |
| 40 | Typo, like all Rails apps, doesn't work well as a CGI. Seriously consider |
| 41 | using FastCGI instead. To deploy on FastCGI you will need to follow the setup |
| 42 | instructions on the typo page at http://www.typosphere.org/trac/wiki/FastCgi |
| 43 | |
| 44 | By default, Typo runs in *development* mode. This is very useful for |
| 45 | developers, but it can cause horrible performance for users who aren't |
| 46 | changing Typo's code. Production mode can easily be 20x as fast as development |
| 47 | mode. To change the default, edit the second line of config/environment.rb and |
| 48 | change 'development' to 'production', or follow the directions on the FastCGI |
| 49 | configuration page on the Typo wiki. |
| 50 | |
| 51 | Permissions |
| 52 | =========== |
| 53 | |
| 54 | Typo needs write access to several directories in order to function |
| 55 | correctly. These need to be writable by the user that runs the Typo |
| 56 | process--in a hosted environment this may be your user; on dedicated |
| 57 | systems it may be something like 'httpd' or 'www-data'. |
| 58 | |
| 59 | The specific directories in question are 'log/' (and everything underneath |
| 60 | it), 'cache/', and 'public/'. Strictly speaking, Rails will continue to work |
| 61 | if public isn't writable, but Typo's page caching code will work properly and |
| 62 | this will cause Typo to be slower and use much more CPU time. For the security |
| 63 | conscious, Rails really only needs the ability to change a half-dozen files |
| 64 | and subdirectories under public/, ask on the Typo mailing list for more |
| 65 | details. |
| 66 | |
| 67 | Usage |
| 68 | ====== |
| 69 | |
| 70 | Typo's administrative interface is available at |
| 71 | http://your.domain.com/admin. You can use this to post articles and |
| 72 | change Typo's configuration settings. For posting new content, you can |
| 73 | either use this administrative web interface or a desktop blog editor |
| 74 | like MarsEdit or Ecto. For a short list of clients which are confirmed |
| 75 | to work please visit http://typosphere.org/trac/wiki/DesktopClients. |
| 76 | |
| 77 | Client setup |
| 78 | ============ |
| 79 | |
| 80 | Set your desktop client to Movable Type API and enter |
| 81 | http://your.domain.com/backend/xmlrpc as endpoint address. |
| 82 | |
| 83 | Tell me about your blog |
| 84 | ======================= |
| 85 | |
| 86 | Add yourself to the list of typo blogs at http://typosphere.org/trac/wiki/TypoPowered |
| 87 | and subscribe to the typo mailing list. |
| 88 | |
| 89 | |
| 90 | Enjoy, |
| 91 | Your typo team |
| 92 |
