sqlite3 gem required? should i finally install sqlite?

Sure. HOWEVER.

well that is odd, I can’t paste in the actual data, and escape characters cause everything to asplode. attempting a wink wink nudge nudge

Yeah, when you start Park Place, you’ll see XML .

• /control for the admin.
• /tracker to see served torrents.

Warning is good, but many have already unknowingly installed the sqlite3-evil gem. Can we do better?

I’ve found you can tell whether or not you’ve been given the bad version of sqlite3 by attempting a require 'sqlite3_api'. If you see sqlite3 but not sqlite3_api, you know you’re about to imbibe the bad juice.

Best: trap the LoadError from the sqlite3_api attempt, and print a meaningful error message about what the user needs to do to fix things.

That way, things always fail up front and people know why and what to do.

I wanted to do this for Camping, actually, but there I was stuck on how to do this check only when somebody tried to use the :sqlite3 backend. It should be easier here if sqlite3 is the only option.

tuff_ghost.mp3? does someone like the unicorns?!

Okay, well, a new gem is up. None of the images and colors were loading previously.

MenTaLguY: Alright, thanks for doing the footwork on that. The new gem does just that.

nil: Good point. Is now fixed.

Justin Camerer: It’s the stuff dead musclemen are made of.

MenTaLguY: From irb on my freebsd box dropping require 'sqlite3' and require 'sqlite3_api' both throw fits, but sqlite3-ruby was installed w/ SWIG and SQLite3 backing although I did drop a ruby-sqlite3 from the ports databases section. more research is needed?

for those following the bouncing ball. go grab s3Dav.0.6 pry apart org.carion.s3dav.s3.keymanagement:CredentialImpl.java Line 42, drop in what host you wish. “Localhost:10102” works wonders for me (ssh tunnel) Eclipse->Ant->Build :D

conversly I can NOT get this mess to upload :)

If mongrel’s hanging when you upload, I’d force a fresh install:

 gem install mongrel --source code.whytheluckystiff.net

I made a slight update to the gem.

updated to mongrel-0.3.12.5/ Still having issues using s3Dav, but I believe the issues lie w/ s3Dav. It seems to be having issues w/ sockets. Guess I’ll get my hands dirty tommorow night and whip up something better.

nil: well, if you’re just firing up an irb session, you do have to require rubygems before you can get at either sqlite3-ruby or sqlite3-evil.

(I actually made the same mistake a couple times myself.)

ooopps sorry :)

Hrm, the /tracker isn’t showing anything.
That’s odd. My bucket and everything is set up public-read. Perhaps it’s because it’s listening on 0.0.0.0?

Nothing gets seeded until the torrent file is requested.

And I’d stay away from 0.0.0.0. Use your most public interface. Later you can veil it. But it’ll just frustrate you while you’re testing.

Being stuck behind a NAT “Intarwub-gateway-in-a-box” that I can’t get rid of (it does our Vonage), I get errors trying to bind to the public address. How might one go about requesting a torrent from parkplace?

Wow. I really need to read the post better next time.

Looking forward to the rubyTorrent gem for my RubyTV script.

Parkplace runs fine, but I am unable to authenticate from the Amazon ruby code. The problem seems to be related to the headers: as I enter module ParkPlace::S3#service, @env has {“SERVER_NAME”=>“ishtar”, “HTTP_CONTENT_TYPE”=>”/\r\nContent-Type: ”... Note the mashed up accept and Content-Type: headers. Where are the headers extracted, mongrel? [all code downloaded today—platform is Linux]