From matijs at matijs.net  Sun Apr 17 05:27:52 2011
From: matijs at matijs.net (Matijs van Zuijlen)
Date: Sun, 17 Apr 2011 11:27:52 +0200
Subject: [typo] Installation typo6.0.4 failed on Ruby 1.9.2 and
	rails3.0.5
In-Reply-To: <9d33f24180997d39d1d75ad2bea3754e@ruby-forum.com>
References: <9d33f24180997d39d1d75ad2bea3754e@ruby-forum.com>
Message-ID: <4DAAB298.9000202@matijs.net>

Hi Ken,

On 03/24/2011 02:48 AM, ken wang wrote:
> I installed the sqlite3,and also copied the sqlite dll to ruby's bin
> dir. Anyone can tell me what's wrong with my opeoration?
> 1 When using the default database.yml, and change the password to my
> local paasword.
> When exec bundle install, mysql 2.8.1 is installed.
> Then exec rake RAILS_ENV=production db:create, return already exists as
> ECHO1 in attachs:

If you want to use sqlite3, you have to also set the adapter to sqlite3 in the 
database.yml. Since you didn't do that, bundler will install mysql for you.

Segmentation faults in Ruby are really outside the scope of Typo. You may have 
better luck contacting a mailing list related to the mingw distribution of Ruby 
you're using.

> 2 I changed the configuration of database and gemfile. Replace all the
> mysql to mysql2.
> When exec bundle istall, it using the mysql2 (0.2.6)
> When exec rake RAILS_ENV=production db:migrate, returns as ECHO2 in
> attachs:

This looks more promising ...

> 3 when change the database config as follows:
> production:
>    adapter: mysql2
>    encoding: utf8
>    database: typo
>    pool: 5
>    username: root
>    password: '123456'
>
> development:
>    adapter: mysql2
>    encoding: utf8
>    database: typo_dev
>    pool: 5
>    username: root
>    password: '123456''
>
> rake RAILS_ENV=production db:create is successful
> rake RAILS_ENV=production db:migrate failed in the executing. As ECHO3
> in attachs::

Now this is interesting :-). It seems this fails with Ruby 1.9.2, whereas it 
works fine with Ruby 1.8.7.

I've made a patch that fixes this error (see attachment). You will have to 
re-create the database, so do a db:drop, db:create, db:migrate.

I will commit this patch to github as well.

> Attachments:
> http://www.ruby-forum.com/attachment/6069/typo_failed.txt

Regards,
-- 
Matijs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: protected_with_scope.patch
Type: text/x-patch
Size: 1157 bytes
Desc: not available
URL: <http://rubyforge.org/pipermail/typo-list/attachments/20110417/a1943805/attachment.bin>

From henry74 at gmail.com  Mon Apr 18 14:41:16 2011
From: henry74 at gmail.com (henry74)
Date: Mon, 18 Apr 2011 13:41:16 -0500
Subject: [typo] Typo 6.0.4 memory usage
Message-ID: <BANLkTim7dYdj-+pTuKCR=5sOfPRXYE1KaA@mail.gmail.com>

I recently upgraded to the latest version of Typo and I'm noticing
considerably more memory usage.  I'm using an nginx proxy in front of 3 thin
servers and I'm seeing about 190MB per thin instance which is causing my
server to start using swap.  I didn't have this issue with earlier versions
of Typo.

Is anyone else experience higher than normal memory usage with the recent
version of Typo?

Thanks,
Henry
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/typo-list/attachments/20110418/0c5d2e80/attachment.html>