Typo 4.0.1

Posted by Scott Laird Thu, 10 Aug 2006 07:22:03 GMT

I just released Typo 4.0.1. By and large, this is a bug-fix release. Please make sure that you use Typo 4.0.1 with Rails 1.1.5, as earlier versions (1.1.4 especially) have substantial security problems.

A number of changes were made to the installer for this release:

  • It has been spun off into its own .gem and lives in its own source repository, so other projects can use it as well.
  • It now supports Postgres as well as SQLite3. I’ll write about this soon.
  • It performs database-agnostic backups to a .yml file.
  • A number of bugs have been squashed.

If you installed Typo 4.0.0 via the new installer, then upgrading is easy–just gem install typo and then typo install /some/path to upgrade. If you’re using the tar or zip files from Rubyforge, then unpack them over the top of your existing install, run ‘gem install rails’ to make sure that you have Rails 1.1.5, run ‘rake migrate’, and then restart your FastCGI processes.

If you’re installing for the first time, then you’ll probably find the .gem installer to be easier. If you can install things as root (or your hosting provider has already installed the Typo .gem), then do this:

  $ sudo gem install typo
  $ typo install /some/path

If you don’t have the ability to run gem install as root, then do this:

  $ export GEM_PATH=~/gems
  $ gem install -i ~/gems typo
  $ ~/gems/bin/typo install /some/path

As usual, let me know if you hit problems.

Tags , ,  | 10 comments

Comments

  1. Wijnand said about 5 hours later:
    Well, I do run into troubles with this release. It seems updating does not work very well yet.. wijnand@jabber:~/typo$ typo install . Stopping Typo Sending TERM to Mongrel at PID 4482…Done. /usr/lib/ruby/gems/1.8/gems/rails-app-installer-0.1.1/lib/rails-installer.rb:173:in `backup_database’: undefined method `backup’ for nil:NilClass (NoMethodError) from /usr/lib/ruby/gems/1.8/gems/rails-app-installer-0.1.1/lib/rails-installer.rb:117:in `install_sequence’ from /usr/lib/ruby/gems/1.8/gems/rails-app-installer-0.1.1/lib/rails-installer.rb:104:in `install’ from /usr/lib/ruby/gems/1.8/gems/rails-app-installer-0.1.1/lib/rails-installer/commands.rb:95:in `command’ from /usr/lib/ruby/gems/1.8/gems/rails-app-installer-0.1.1/lib/rails-installer.rb:538:in `execute_command’ from /usr/lib/ruby/gems/1.8/gems/typo-4.0.1/bin/typo:38 from /usr/lib/ruby/gems/1.8/gems/activesupport-1.3.1/lib/active_support/dependencies.rb:140:in `load’ from /usr/bin/typo:18
  2. Chris Mc said about 5 hours later:

    I just got the same error. What version of rails-app-installer is current? Does (did) 0.1.1 not have the backup() method yet? I got the same versions as Wijnand from Rubyforge. Is this just a mirror update latency problem?

  3. John said about 8 hours later:

    I get the same error here too…

  4. Scott Laird said about 8 hours later:

    Ugh. It works perfectly for me, and I’ve tested this so much lately that I keep having to kill off piles of mongrel processes.

    What does ‘typo config PATH’ show?

  5. Chris Mc said about 10 hours later:
    $ typo config typo
database=mysql
port-number=4383
rails-environment=production
threads=2
web-server=external
  6. Scott Laird said about 10 hours later:

    Ahh. Okay, that’s what we’re seeing.

    database=mysql and the current installer causes issues, because it half-supports it.

    I’ll straighten it out over lunch today.

  7. Chris Mc said about 10 hours later:

    Groovy! Now if we could just get a properly-patched version of Rails…

  8. John said about 15 hours later:

    Sorry it took a while to check back in,:

    johnm@zero ~/rails_work/blog $ typo config trunk/
database=mysql
port-number=4442
rails-environment=production
threads=2
web-server=mongrel
johnm@zero ~/rails_work/blog $

    I believe the error has something to do with the schema version in the database and it for some reason wanting to do a database migration when installing…

  9. Scott Laird said about 15 hours later:

    John, can you try Typo 4.0.2?

  10. Adam said about 1 month later:

    So once you do the the stuff in SSH what do you do now? I mean I see all the files and stuff? Any one?

    Thanks,

RSS feed for this post

Comments are disabled