Please test Typo 3.99.1 gem

I released a pair of Typo 4.0 pre-release gems yesterday to test out the
new
Typo installer. Can I get a few people to test out the new Typo
3.99.1gem? Do this:

$ gem install typo
$ typo install /some/path

This should create a working Typo install in /some/path. The installer
uses
SQLite and Mongrel to produce a self-contained Typo setup. The next
version
will include directions for setting up HTTP proxying through Apache and
Lighttpd; for now you can either do that yourself or just use Mongrel
directly from your browser.

There are still a handful of things to fix before Typo 4.0 is officially
released, but we’re getting really close now. The big things left are:

  1. Installer: write proxying directions for common web servers.
  2. Installer: document usage
  3. Installer: minor code cleanup
  4. Typo: one last sweep through Trac.
  5. Typo: write a “what’s new in 4.0” document.

Scott

I’m getting a ‘404 Not found’ error when running ‘sudo get imstall
typo’ on my Mac.

You want sudo gem install typo, no get and not imstall.

Good Luck
-Steve
http://www.stevelongdo.com

Related to this http://www.typosphere.org/trac/ticket/920, and there may
be
another ticket for it, is that in the most recent version of the trunk
that
I checked out (might have been 10 days ago), this wasn’t in there, and
also,
the articles were sorted by created_at instead of published_at on the
main
page. Is this fix going to be in 4.0?

Still? It should have been copied to all GEM mirrors by now. It worked
fine for me this morning.

I need to figure out how to do ‘gem install --verbose typo’, and I need
to
figure out where the ‘master’ gem server lives. As things stand, it
takes
3+ hours from the time I upload a gem until it’s usable.

Scott

It’s already in the trunk.

Scott

The documentation is still a work in progress :-).

You can change the port this way:

typo stop /path/to/typo
typo config /path/to/typo port-number=9999
typo start /path/to/typo

The mongrel port number is picked randomly from [4000…4999]. I’d
rather
not use a single fixed port, because I’d like to make
multiple-typos-per-host installs easy. I’ll take suggestions for better
algorithms if anyone has one.

Scott

I just ran gem install typo and it seemed to work. I can’t test it yet
though, I think because my host blocks port 4517, which seems to be the
port
typo choose to start mongrel on. At the end of the install, if says
this:

Look in installer/apache.conf.example to see how to integrate with
Apache.

Except there is no file called apache.conf.example in there.

I did a clean install first, that worked. Then I tried to upgrade an
existing typo, and I got this:

copying /test/mocks/themes/123-numbers-in-path/about.markdown
copying /test/mocks/themes/CamelCaseDirectory/about.markdown
copying /test/mocks/themes/azure/about.markdown
/usr/lib/ruby/1.8/fileutils.rb:243:in mkdir': File exists - /home/paulbarry/typo/test/mocks/themes/azure (Errno::EEXIST) from /usr/lib/ruby/1.8/fileutils.rb:243:infu_mkdir’
from /usr/lib/ruby/1.8/fileutils.rb:217:in mkdir_p' from /usr/lib/ruby/1.8/fileutils.rb:215:inmkdir_p’

So then I just did a clean install again, then copied over my sqlite
files
and my theme files, ran rake db:migrate (which did nothing) and then I
got
my “upgraded” site.

The main page still sorts by created_at and the permalinks are generated
from created_at.

Thanks. I haven’t fully dealt with the “upgrade an existing typo” case
yet,
and the created_at/published_at fix went into the trunk after 3.99.1 was
frozen. I’ll try to spit out 3.99.2 in the next 24 hours, once I’ve had
a
few more bug reports.

Scott

Can mongrel be bound to UNIX sockets like FCGI or does it only work with
ports? It would be nice if the tmp/sockets/ directory could be the
default
instead of a port.

I have rails & mongrel & sqlite3-ruby all set up on Windows, and it
seems to install and run fine. There are a few “path not found”
messages, and the tests claimed to have failed, but it seems to run.

Scott, thanks for taking the time to work on Typo. Rails needs typo,
IMHO, and I’m happy to run my blog on a Rails app rather than …
anything else. :slight_smile:

On 7/6/06, Scott L. [email protected] wrote:

multiple-typos-per-host installs easy. I’ll take suggestions for better
typo choose to start mongrel on. At the end of the install, if says this:
fine for me this morning.

Typo installer. Can I get a few people to test out the new Typo
Typo-list mailing list


Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list


Cheers,

Kevin

To the best of my knowedge, it only uses ports. I’ve never seen a HTTP
proxy that can bind to unix domain sockets.

If you’d like, you can say ‘typo config PATH bind-address=127.0.0.1’,
and
then restart typo. That’ll tell Mongrel to bind to localhost.

Scott

Out of curiosity, which tests failed? cd to the new Typo directory and
run
‘rake test’. It’d be nice to get all of the test failures fixed.

Scott

AFAIK, no. It’s an http server only, and http is a tcp protocol.

It’s an interesting idea, though. Perhaps a plugin could be written? I
don’t know. Interesting idea, for sure.

On 7/6/06, Steve L. [email protected] wrote:

typo choose to start mongrel on. At the end of the install, if says this:

Still? It should have been copied to all GEM mirrors by now. It

out the new

http://hronia.blogalia.com
[email protected]


Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list


Cheers,

Kevin

On 7/6/06, Scott L. [email protected] wrote:

Still? It should have been copied to all GEM mirrors by now. It worked
fine for me this morning.

It has just worked fine right now. Five minutes ago it failed.

And no typos this time :slight_smile:

No problem, I realized that I don’t actually really need my created_at
and
published_at to be different, so I just ran “update contents set
created_at
= published_at” as a work around for the problem. I just had some old
entries that I migrated over from a different blog, and I wanted them to
show up with the original published_at.

This is really helpful, because setting up everything is kind of
overwhelming and painful. I like the idea that you are saying
mongrel/sqlite is the way to go for a basic vps hosted blog, that should
make the install a lot less painful for other people.

The gem download servers are load balanced, so one bad server can
probably
cause intermittent problems. I’m not sure what the best way around this
is.

Scott

All tests passed.

On 7/6/06, Scott L. [email protected] wrote:

messages, and the tests claimed to have failed, but it seems to run.

typo stop /path/to/typo
Scott

worked

I released a pair of Typo 4.0 pre-release gems yesterday to test


http://rubyforge.org/mailman/listinfo/typo-list


Typo-list mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/typo-list


Cheers,

Kevin

On 7/6/06, Scott L. [email protected] wrote:

I released a pair of Typo 4.0 pre-release gems yesterday to test out the new
Typo installer. Can I get a few people to test out the new Typo 3.99.1 gem?
Do this:

$ gem install typo
$ typo install /some/path

I found that the path must be an absolute path. ‘typo install
./typo’ failed with chdir throwing (Errno::ENOENT) Maybe the docs
should state this more clearly.

On the other hands, some tests failed, this is the trace:

Tamarindo:~/Sites/typo juan$ rake test --trace
(in /Users/juan/Sites/typo)
** Invoke test (first_time)
** Execute test
** Invoke test:units (first_time)
** Invoke db:test:prepare (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute db:test:prepare
** Invoke db:test:clone (first_time)
** Invoke db:schema:dump (first_time)
** Invoke environment
** Execute db:schema:dump
** Execute db:test:clone
** Invoke db:schema:load (first_time)
** Invoke environment
** Execute db:schema:load
** Execute test:units
/usr/local/bin/ruby -Ilib:test
“/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader.rb”
“test/unit/article_test.rb” “test/unit/audioscrobbler_test.rb”
“test/unit/blacklist_pattern_test.rb” “test/unit/blog_test.rb”
“test/unit/category_test.rb” “test/unit/comment_test.rb”
“test/unit/configuration_test.rb” “test/unit/delicious_test.rb”
“test/unit/flickr_test.rb” “test/unit/fortythree_test.rb”
“test/unit/magnolia_test.rb” “test/unit/metafragment_test.rb”
“test/unit/notification_mailer_test.rb” “test/unit/observer_test.rb”
“test/unit/page_cache_test.rb” “test/unit/page_test.rb”
“test/unit/ping_test.rb” “test/unit/redirect_test.rb”
“test/unit/resource_test.rb” “test/unit/sidebar_test.rb”
“test/unit/tag_test.rb” “test/unit/text_filter_test.rb”
“test/unit/theme_test.rb” “test/unit/trackback_test.rb”
“test/unit/trigger_test.rb” “test/unit/user_test.rb”
“test/unit/content_state/factory_test.rb”
Loaded suite
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader
Started

Finished in 16.85309 seconds.

141 tests, 458 assertions, 0 failures, 0 errors
** Invoke test:functionals (first_time)
** Invoke db:test:prepare
** Execute test:functionals
/usr/local/bin/ruby -Ilib:test
“/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader.rb”
“test/functional/accounts_controller_test.rb”
“test/functional/articles_controller_test.rb”
“test/functional/backend_controller_test.rb”
“test/functional/redirect_controller_test.rb”
“test/functional/textfilter_controller_test.rb”
“test/functional/theme_controller_test.rb”
“test/functional/xml_controller_test.rb”
“test/functional/admin/article_preview_test.rb”
“test/functional/admin/blacklist_controller_test.rb”
“test/functional/admin/categories_controller_test.rb”
“test/functional/admin/comments_controller_test.rb”
“test/functional/admin/content_controller_test.rb”
“test/functional/admin/general_controller_test.rb”
“test/functional/admin/pages_controller_test.rb”
“test/functional/admin/resources_controller_test.rb”
“test/functional/admin/textfilters_controller_test.rb”
“test/functional/admin/themes_controller_test.rb”
“test/functional/admin/trackbacks_controller_test.rb”
“test/functional/admin/users_controller_test.rb”
Loaded suite
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake/rake_test_loader
Started
…E…
Finished in 71.014778 seconds.

  1. Error:
    test_comment_spam_markdown_smarty(ArticlesControllerTest):
    ActiveRecord::Transactions::TransactionError: Transaction aborted
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/transactions.rb:84:in
    transaction' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/transactions.rb:84:intransaction’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/transactions.rb:118:in
    transaction' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/associations/association_collection.rb:124:inreplace’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/associations.rb:895:in
    notify_users=' /Users/juan/Sites/typo/config/../app/models/article.rb:180:inadd_notifications’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/callbacks.rb:333:in
    callback' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/callbacks.rb:330:incallback’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/callbacks.rb:260:in
    create_without_timestamps' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/timestamp.rb:30:increate’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/base.rb:1718:in
    create_or_update_without_callbacks' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/callbacks.rb:249:increate_or_update’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/base.rb:1392:in
    save_without_validation' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/validations.rb:724:insave_without_transactions’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/transactions.rb:126:in
    save' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb:51:intransaction’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/transactions.rb:91:in
    transaction' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/transactions.rb:118:intransaction’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/transactions.rb:126:in
    save' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/base.rb:1398:insave_without_validation!’
    /Users/juan/Sites/typo/config/…/vendor/rails/activerecord/lib/active_record/validations.rb:734:in
    save!' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/validations.rb:699:increate!’
    ./test/functional/articles_controller_test.rb:27:in
    setup_without_fixtures' /Users/juan/Sites/typo/config/../vendor/rails/activerecord/lib/active_record/fixtures.rb:548:insetup’

204 tests, 792 assertions, 0 failures, 1 errors
rake aborted!
Test failures
/Users/juan/Sites/typo/config/…/vendor/rails/railties/lib/tasks/testing.rake:35
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:in
execute' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:387:inexecute’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:357:in invoke' /usr/local/lib/ruby/1.8/thread.rb:135:insynchronize’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:350:in invoke' /usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:inrun’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/lib/rake.rb:1906:in `run’
/usr/local/lib/ruby/gems/1.8/gems/rake-0.7.1/bin/rake:7
/usr/local/bin/rake:18

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs