Re: How to lock Typo to Rails 1.0?

Ruby Apps Typo
1

Try running:

rake freeze_edge REVISION=3303

On your Typo install directory. This is the equivalent to the Rails 1.0gem.

Thanks Steve, that works. But the whole purpose of RubyGems is so
that you could have multiple versions of gems installed and have your
Ruby app require a specific version – does this not work with Rails
at all?

Sean

2

Sean M. <smountcastle gmail.com> writes:

at all?

Sean

To lock your “require” to a specific version you can follow the
instructions from
http://wiki.rubyonrails.com/rails/pages/HowtoLockToSpecificRailsVersions

Maybe the environment.rb from typo should use this?

Thanks,
Pascal.

3

‘rake freeze_edge REVISION=3303’
Isn’t that REVISION=3301 Steve?There is no revision 3303 in the svn
repository, but there is arevision 3301, with a date of December 13,
2005, corresponding to therelease date of Rails 1.0. Next revision
number is 3314.
david richardson

4

I think the issue with this might be that the Typo environment.rb
includes
the vendor/rails/*/lib in the config.load_paths and that might be why:

require_gem ‘rails’, ‘= 1.1.0’

doesn’t work so good. Really the Typo team dropped the ball on this
one, it
isn’t like they didn’t know that Rails 1.1 was coming or that they were
going to have problems. I am disappointed with the response from them
which
has been near silence.

Even when they are ready the memory consumption/CPU usage now exceeds
the
max per process on Textdrive. So without some clean up to the codebase
people will be in for a shock when they can get to Rails 1.1 and Typo
4.0 on
a shred host because it will get killed anyway. sigh

5

On Mar 29, 2006, at 4:08 PM, David R. wrote:

‘rake freeze_edge REVISION=3303’
Isn’t that REVISION=3301 Steve?There is no revision 3303 in the svn
repository, but there is arevision 3301, with a date of December
13, 2005, corresponding to therelease date of Rails 1.0. Next
revision number is 3314.

If you’re looking at the log of trunk, then yes, there’s no revision
3303. That’s because revision 3303 is the revision at which the
rel_1-0-0 tag was created. So checking out trunk at that revision is
the same as checking out the tag, effectively (since the tag is a
copy of trunk at that revision).

6

On 3/29/06, Kevin B. [email protected] wrote:
[snip]

Rails 1.1, we’ll update trunk and tell everybody to upgrade rails.
First off, thanks to everyone who is working on Typo in their spare
time.

I think one major thing that could’ve helped prevent this problem was
having a page up somewhere to point people to detailing the problems
with Rails 1.1 and Typo and showing how to freeze at 1.0. I dunno how
the conflict has been known, but I know I only saw the topic discussed
on this list a few days before 1.1 dropped. IRC is great for some
people, but its really no substitute for a FAQ or wiki to point people
to reach the wider user base.

7

Sorry if my language seemed inflammatory. I’ve had lots of super bad
experiences with IRC botware so I stay out of there. I imagine a
sizable
percentage of Typo users don’t go there either. We do check the mailing
list or the in transit typosphere.org website.

I have had some success with removing the sidebars code from my install
to
reclaim some memory. I also switched the environment.rb to not load
actionwebservice which does prevent webservice access to my blog, but I
mostly go through the admin web interface anyway. Application.rb has a
line
mentioning to use cache_pages instead of cache_actions_with_params in
memory
constrained environments. These changes have dramatically dropped my
memory
use on TXD. Stabilizing it at around 37-42M. So I have worked around
the
memory limit there, but CPU% will still exceed 10% for more than 60secs
and
the OS kills processes on TXD that do that…

I have noticed even on my Mac when using the admin interface to post an
article the live update applies filters, etc. and causes a huge spike in
CPU
usage. I have taken to editing my posts locally and then pasting them
into
my textdrive account. Sometimes CPU will just spike though… :frowning:
I’ve
found a lot of information on memory profiling for Ruby on line but
nothing
about reducing CPU cycles. Perhaps being able to toggle the live update
versus a preview post button would help here?

Please don’t take my comments as an attack on you or Team Typo, I just
think
that communication through channels other than IRC might have been a
good
way to let the unwashed masses of Typo users know what was going on.
I’ve
seen the trac timeline and can tell that you and Scott and Piers have
been
very busy trying to get things cleaned up today. Again no disrespect
was
intended. I have been a happy Typo user for some time now and don’t
want to
jump ship to gasp PHP or anything else. It would be good if there was
a
1.1 release project with the known compatibility issues on Trac, I am
sure
that myself and other capable ruby programmers would be happy to provide
some patches to help you guys get through this transition quicker.

8

On Mar 29, 2006, at 2:09 PM, Steve L. wrote:

I think the issue with this might be that the Typo environment.rb
includes the vendor/rails/*/lib in the config.load_paths and that
might be why:

require_gem ‘rails’, ‘= 1.1.0’

doesn’t work so good.

I looked at this the other day and environment.rb actually includes
boot.rb which does a ‘require’ for a file inside the rails gem, so I
wasn’t sure what the right way was to lock it to a specific rails
(since I figured there might be a good reason why it was requiring
just that one file and not the whole gem).

Really the Typo team dropped the ball on this one, it isn’t like
they didn’t know that Rails 1.1 was coming or that they were going
to have problems. I am disappointed with the response from them
which has been near silence.

Near silence? I take it you never even bothered to drop by the IRC
channel #typo (on freenode) where we’ve been discussing this for some
time. The problem is that there’s apparently no way to maintain both
1.0 and 1.1 compatibility with Typo (don’t know why, but that’s what
we’ve discovered) and so we decided to hold off updating until 1.1
was actually out the door. And now that it is, we’ve been working on
getting Typo running on it. If you look at the IRC channel we have
instructions for locking Typo to 1.0 rails (using the rake freeze_edge REVISION=3303 trick) and warnings that Typo trunk only
works on 1.0. And once our new branch has been verified to work on
Rails 1.1, we’ll update trunk and tell everybody to upgrade rails.

Even when they are ready the memory consumption/CPU usage now
exceeds the max per process on Textdrive. So without some clean up
to the codebase people will be in for a shock when they can get to
Rails 1.1 and Typo 4.0 on a shred host because it will get killed
anyway. sigh

That’s actually a problem with TextDrive. We don’t know why it
happens, but TextDrive causes Typo to use approximately twice as much
RAM as every other system I’ve seen statistics on. I don’t know what
to do about it.

9

A big part of the problem is the MIA TypoSphere.org website. Is it
ahosting problem or is there no-one to get the job done?
david richardson--www.channel200.net

10

“Steve L.” [email protected] writes:

Please don’t take my comments as an attack on you or Team Typo, I just think
that communication through channels other than IRC might have been a good
way to let the unwashed masses of Typo users know what was going on. I’ve
seen the trac timeline and can tell that you and Scott and Piers have been
very busy trying to get things cleaned up today. Again no disrespect was
intended. I have been a happy Typo user for some time now and don’t want to
jump ship to gasp PHP or anything else. It would be good if there was a
1.1 release project with the known compatibility issues on Trac, I am sure
that myself and other capable ruby programmers would be happy to provide
some patches to help you guys get through this transition quicker.

A lot of the time they’re such niggling little things that we haven’t
bothered adding trac tickets for them because generally, as soon as
you can work out how to explain what the problem is in a ticket,
you’ve worked out how to fix it.

But your point is well made, and taken.

11

Kevin B. [email protected] writes:

It’s not exactly MIA. There’s a link there that leads you to
Typo - which is identical to the old typo.leetsoft.com.
It’s just that we wanted to build a nicer site around typosphere and
currently there’s been no progress (that I’m aware of, at least) on
this regard.

I’m not even sure what the concrete plans are for this.

Piers? Scott? Tobias (if you’re listening)?

I had vaguely thought of having a front paged, multi-authored typo
blog. Use static stuff in the sidebar to link into the trac and
elsewhere and generally keep people informed. Plus, eating your own
dogfood never hurts.

12

On 3/30/06, Piers C. [email protected] wrote:

I had vaguely thought of having a front paged, multi-authored typo
blog. Use static stuff in the sidebar to link into the trac and
elsewhere and generally keep people informed. Plus, eating your own
dogfood never hurts.

It might be worth redirecting to the trac page, since the typosphere
“in progress” page has been up for so long and I’m betting a lot of
users never make it past there. I wouldn’t be surprised if new users
blow right past the download links and the trac link and assume that
the site is just MIA for now.

13

It’s not exactly MIA. There’s a link there that leads you to
Typo - which is identical to the old typo.leetsoft.com.
It’s just that we wanted to build a nicer site around typosphere and
currently there’s been no progress (that I’m aware of, at least) on
this regard.

I’m not even sure what the concrete plans are for this.

Piers? Scott? Tobias (if you’re listening)?

14

I’m not even sure what the concrete plans are for this.Question answered.
I will get this going if someone wants to contact me.
david richardson–www.channel200.net

15

Piers C. wrote:

I had vaguely thought of having a front paged, multi-authored typo
blog. Use static stuff in the sidebar to link into the trac and
elsewhere and generally keep people informed. Plus, eating your own
dogfood never hurts.

Could someone at least setup redirects at typo.leetsoft.com so all
requests for /trac are forwarded to the typosphre.org/trac ? That is one
of my major gripes with the whole website move.

Regards,
Jason