Migratory Ape

Without much (or as far as I can tell, any) fanfare, Tim’s APE has moved from java.net to rubyforge.  And moved from cvs to svn.  But rest assured, other than the location and the repository type (and code layout, dependencies, and functionality) nothing much has changed.  Really.  Just don’t try to look at Dave Johnson or my notes as they will just confuse you.

If you do manage to check the file out, you see a Rakefile.  This would imply that one might want to use rake.  Trying it results in a message

You are missing a dependency required for meta-operations on this gem.
No such file to load -- echoe

Then after a sudo gem install echoe, you get the following:

undefined method `exclude' for nil:NilClass
/home/rubys/svn/ape/Rakefile:5

Then giving up on the Rakefile, one can do the following:

sudo gem install erubis mongrel

export URI=https://rubix.home/wordpress/wp-app.php/service
export USERNAME=rubys
export PASSWORD=password

export RUBYLIB=lib/ape
ruby scripts/go.rb "uri=$URI&username=$USERNAME&password=$PASSWORD") > report.html

Of course, you might want to adjust the URI, USERNAME, and PASSWORD to taste.

The end result looks something like this, presuming that you first copy lib/ape/layout/* to ../ape, which of course should be intuitively obvious.

Hmmm.  It looks like I’m now getting 10 warnings where I used to get 4.  Apparently Ape now complains when it sees an extra blank line, and somewhere along the way WordPress stopped sanitizing.  It shouldn’t be too hard to track down which changeset caused the latter problem.

And some people wonder why some open source projects have a hard time attracting developers.


I am delighted to announce that my collaborators (now including Brandon Mitchell) have been wrangling the Ape and it is now a Ruby Gem. Wow.

We’ve transformed a lot of scripts in a ruby gem that provides a Mongrel based server. Once the ape gem is installed and this server is running, the web interface is available in the port 4000 of your localhost.

  $ sudo gem install ape && ape_server

Posted by Iain at

That certainly is cool.  But being able to run from svn is a prereq for developers who might be willing to contribute patches...

Posted by Sam Ruby at

Hmm, the source links in that comment seem to have disappeared; I’m sure they were there in the preview? Neither paragraph is mine.

manually this time:
Tim’s Ape post
ape/gem announce,  linked from ongoing

Posted by Iain at

Argh. Sam, your preview is showing the links but stripping them from the textarea  so that when I submit, they’re missing. Is javascript required?

Suffice to say that tim mentioned the ape move on ongoing the other day.

Posted by Iain at

Tim mentioned the gem.  But still says that the source code may be found at ape.dev.java.net.

I run an hourly regression test, using the latest Ape from cvs (now svn).  Only when I caught Tim via IM did he tell me about the repository move.

Gems are great, but for those of us who may be predisposed to submitting patches, knowing how to run from SVN is indispensable.

Links seem to work for me.

Posted by Sam Ruby at


One thing I’ve noticed, Sam, is that a lot of open source is along the lines of “here, I’ve published this so you can see what I’m working on.” Which isn’t really a shipping software mentality, but satisfies other needs like finding potential soulmates and some amount of self-promotion.

For better or worse. I wish that more publicly available code was at the same turnkey level that you offer. I wish for a lot of things. But in general, hammering out a 1.0 version that “runs on my machine” is easier than “making something people can use themselves.” My hope in these cases is that the interest level is maintained to love and care for it up to the point where it’s actually usable by someone else, but that may not be an interesting itch to scratch.

And yeah, what kind of self-promotion is it if it falls over and catches on fire? Good question.

Posted by Blake Ramsdell at

a lot of open source is along the lines of “here, I’ve published this so you can see what I’m working on.”

A lot of the source that you will find by clicking on the “code” link on the right hand side of this page falls under that category.

My hope in these cases is that the interest level is maintained to love and care for it up to the point where it’s actually usable by someone else, but that may not be an interesting itch to scratch.

One thing that often does help is very detailed bug reports describing what you attempted, what failed, and how (ultimately) you got something to work.

Things like what I Dave posted in June and I posted in August.  And, for that matter, like what I posted today.

Posted by Sam Ruby at

YAGNI.  Put something out there, if people complain, fix it.  That’s what we did, and as chance would have it, got the setup problem fixed today.

Posted by Assaf Arkin at

svn checkout, rake setup

Sam Ruby on the trials of getting Ape to run from SVN: If you do manage to check the file out, you see a Rakefile. This would imply that one might want to use rake. Trying it results in a message “You are missing a dependency required for...

Excerpt from Labnotes at

Put something out there, if people complain, fix it.

Report card, Ape:

Step 1: check.
Step 2: check.
Step 3: needs improvement.

Posted by Sam Ruby at

AppClientTest Update

I’ve just checked in an updated version of the AppClientTest, a program for testing you AtomPub service. It has been updated to use the atompubbase module and also sports HTML output as an option. To make it easier to develop I’ve transcluded via...

Excerpt from BitWorking | Joe Gregorio at

thank you for your report Sam, we are going to fix them in a few hours.

As you say, developers can contribute, so, we would be happy to receive any patch, improvement or suggestion.

Posted by David Calavera at


Thanks Sam. I added a note to my blog entry and pointed to this post to help reduce the confusion.

- Dave

Posted by Dave Johnson at


Ape fall down go boom

discuss

Posted by Sam Ruby at


Very helpful article. I agree with a previous poster on building from SVN a must-have capability. Good news is that things seem to have improved.

I was able to do the following:

  svn checkout http://ape.rubyforge.org/svn/trunk .
  sudo gem install echoe builder erubis mongrel
  rake manifest
  rake

And got to the point of running tests, unfortunately it seems to be missing a .ape file that it expects to find at /Users/david/.ape rather than /User/:username/.ape. Any ideas on where to find this file?

Output from tests run:

Signal:ape wolf$ rake
(in /Users/wolf/Projects/bliki/3rdparty/ape)
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -Ilib:ext:bin:test "/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/rake_test_loader.rb" "test/unit/authent_test.rb" "test/unit/invoker_test.rb" "test/unit/samples_test.rb" 
Loaded suite /System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/gems/1.8/gems/rake-0.7.3/lib/rake/rake_test_loader
Started
.....F......
Finished in 0.025008 seconds.

  1) Failure:
test_ape_home(SamplesTest) [./test/unit/samples_test.rb:7]:
<"/Users/david/.ape"> expected but was
<"/Users/wolf/.ape">.

12 tests, 16 assertions, 1 failures, 0 errors
rake aborted!
Command failed with status (1): [/System/Library/Frameworks/Ruby.framework/...]


Posted by =Bill.Barnhill at


original bug, recent release

Posted by Sam Ruby at

Add your comment












Nav Bar