Changesets can be listed by changeset number.
The Git repository is here.
- Revision:
- 71
- Log:
Start of upgrade to Typo 4.0.0, the latest stable release since
2.6.0. Note test/mocks/themes/azure changes from a file to a
directory, so the file has been removed in this revision and
the directory will be added in the next revision.
- Author:
- adh
- Date:
- Mon Aug 07 22:18:11 +0100 2006
- Size:
- 5427 Bytes
1 | Typo 4.0 |
2 | ======== |
3 | |
4 | Welcome to Typo 4.0. Typo is a blogging platform, like Movable Typo or |
5 | Wordpress, written using Ruby on Rails. |
6 | |
7 | This is the first major release since Typo 2.6. We skipped Typo 3.0 to avoid confusion with the Typo3 project. |
8 | |
9 | |
10 | Changes since Typo 2.6 |
11 | ---------------------- |
12 | |
13 | * A new installer and a Typo .gem file. Run 'gem install typo' and then |
14 | 'typo install /some/path' to install Typo. |
15 | |
16 | * Text filter plugins, including easy inline Flickr image support and syntax |
17 | highlighting for code. |
18 | |
19 | * Enhanced feed support. Atom 1.0 and RSS 2.0 are both supported. Atom 0.3 |
20 | has been removed. Both feed types have better UUIDs. There are also |
21 | per-tag, -category, and -author feeds. Most pages have their own |
22 | content-specific feeds available via feed autodiscovery. |
23 | |
24 | * Tags. The 'keywords' field in the Typo admin UI (as well as many blog |
25 | editors) has been commandeered to provide tagging for Typo. Tags are |
26 | separated by spaces (just like Flickr). If you want to include a space |
27 | in a tag, then use quotes. |
28 | |
29 | * Improved spam management. There's a "Feedback" tab in the admin interface |
30 | that lists all comments and trackbacks so they can be bulk-deleted. In |
31 | addition, Typo can now use Akismet for spam filtering. |
32 | |
33 | * File uploads. You can now upload images and other content directly from the |
34 | admin UI. |
35 | |
36 | * Podcast support (experimental). |
37 | |
38 | * Email and/or Jabber notification of new content, including comments and |
39 | trackbacks. |
40 | |
41 | * Support for posting articles with a future posting date. Pre-posted |
42 | articles don't appear on the blog or feeds until their posting date passes. |
43 | |
44 | * A new cache system that automatically times out stale entries. Several |
45 | types of content, including the Flickr sidebar, will automatically cause the |
46 | page to be rebuilt every few hours to ensure freshness. |
47 | |
48 | * Better theme support. Some of this was back-ported to Typo 2.6.0. |
49 | |
50 | * A redirect table to help users migrating to Typo. You can enter new URLs |
51 | into the Redirect table and Typo will look there whenever it doesn't |
52 | recognize a URL. So you can move from Movable Type-style permalinks to |
53 | Typo-style permalinks without losing the perma- in your links. |
54 | |
55 | * Cleaner migrations. |
56 | |
57 | * Rails 1.1 support. Rails 1.1.4 is strongly recommended. Rails 1.0 won't |
58 | work at all. |
59 | |
60 | * Improved sidebar support, with a cleaner API and more built-in sidebars. |
61 | |
62 | * Google sitemap support. |
63 | |
64 | * Gravatars support for comments. |
65 | |
66 | * Comment previews. |
67 | |
68 | * Markup help for comments, articles, and pages. |
69 | |
70 | |
71 | How to Install Typo |
72 | ------------------- |
73 | |
74 | There are two ways to install Typo: automatically, using the new Typo installer, or manually, by downloading the source and building a working Rails environment (database, etc) for it. |
75 | |
76 | New users should use the installer wherever possible because it's substantially easier and less trouble-prone. |
77 | |
78 | |
79 | ### Installing Typo via the Typo Installer |
80 | |
81 | You'll need the following software installed on your system: |
82 | |
83 | 1. Ruby 1.8.4 |
84 | 2. RubyGems (http://www.rubygems.org) |
85 | 3. SWIG (http://www.swig.org) |
86 | 4. SQLite 3 |
87 | |
88 | Most Linux distributions should have these easily available. OS X users can |
89 | probably use the 'Locomotive' Rails installer, and there is probably something |
90 | similar available for Windows users. |
91 | |
92 | Once these prerequisites have been installed run these two commands: |
93 | |
94 | $ gem install typo |
95 | $ typo install /some/path |
96 | |
97 | The first command will download the latest Typo release, along with a bunch of |
98 | dependencies. The second command will create a new Typo install in |
99 | `/some/path` (you'll probably want to use a path like `/var/www/typo` instead, |
100 | or `/tmp/typo` if you're just testing things out). The Typo installer will |
101 | create a SQLite database, create all of the tables needed for Typo, and then |
102 | run a battery of tests to make sure that everything works successfully on your |
103 | system. When that's complete, it'll start up the Mongrel webserver on a |
104 | random TCP port. You can access Typo directly via Mongrel for testing, and |
105 | then you can use the installer's directions to set up a more permanent hosting |
106 | environment. |
107 | |
108 | The same process can be used to upgrade Typo in the future--just run `gem |
109 | install typo` to upgrade the version of the Typo installer on your system, |
110 | then run `typo install /some/path` to upgrade your existing Typo install. The |
111 | installer will back up your database, apply changes, re-test your environment, |
112 | and then restart Mongrel. |
113 | |
114 | |
115 | ### Installing Typo Manually |
116 | |
117 | The manual installation process is only recommended for experienced Rails |
118 | users, or people with an existing pre-4.0 Typo install. You'll need to |
119 | download the source for Typo, either via the .zip and .tar files on Rubyforge |
120 | or via Subversion. Then create a database for Typo by hand and populate it |
121 | using the schema files in `db/schema.*.sql`. At this point, run |
122 | `./script/server` to verify that Typo works successfully, and then set up |
123 | either Mongrel or FastCGI to connect Typo to your existing web server. |
124 | |
125 | The full procedure for doing all of this is outside of the scope of this |
126 | document. |
127 | |
128 | |
129 | Support, or where to turn when things break |
130 | ------------------------------------------- |
131 | |
132 | Typo development occurs via http://typosphere.org. If you find a bug, please |
133 | file a bug report via http://typosphere.org/trac/newticket |
134 | |
135 | If you have problems, please send mail to typo-list@rubyforge.org. You can also visit Typo's IRC channel, #typo on irc.freenode.net and ask for help. |