You need to run xmpp_component.rb. That's the provider. You config it via sails.conf. Once that is running, you can run the WebUI and it shuold be able to connect.
I did a small writeup of the steps in the README on Github. I don't want to do anything requiring a bunch of time, such as a video, until I am confrotable with teh basic layout. For example, I think I'm going to rename the wave.danopia.net folder, have a second HTTPd for persistent connections (instant WebUI updates are working on my test copy), do more fancy stuff with DBs so that the provider and persist data, etc. On Nov 2, 8:22 am, Dan Peterson <[email protected]> wrote: > Hey Daniel, > > It's cool to see what you're working on here. I was interested to give the > UI a spin, but I wasn't able to create an account. > > The error that was dumped: > > DRb::DRbConnError in WavesController#index > > druby://:9000 - #<Errno::ECONNREFUSED: Connection refused - connect(2)> > RAILS_ROOT: /www/wave.danopia.net > > Application Trace | Framework Trace | Full Trace > /usr/lib/ruby/1.8/drb/drb.rb:736:in `open' > /usr/lib/ruby/1.8/drb/drb.rb:729:in `each' > /usr/lib/ruby/1.8/drb/drb.rb:729:in `open' > /usr/lib/ruby/1.8/drb/drb.rb:1189:in `initialize' > /usr/lib/ruby/1.8/drb/drb.rb:1169:in `new' > /usr/lib/ruby/1.8/drb/drb.rb:1169:in `open' > /usr/lib/ruby/1.8/drb/drb.rb:1085:in `method_missing' > /usr/lib/ruby/1.8/drb/drb.rb:1103:in `with_friend' > /usr/lib/ruby/1.8/drb/drb.rb:1084:in `method_missing' > /www/wave.danopia.net/app/controllers/application_controller.rb:62:in`connect_remote' > Request > > Parameters: > > None > Show session dump > > Response > > Headers: > > {"Content-Type"=>"", > "Cache-Control"=>"no-cache"} > > Perhaps you could share some screenshots or a video? > > Also, can you elaborate a bit more as to why you can't make waves on your > own server? > > Cheers, > -Dan > > On Thu, Oct 22, 2009 at 1:14 PM, Daniel Danopia <[email protected]> wrote: > > > I have my Ruby provider up and you can use my custom WebUI to do > > anything the Fedone CLI can do, except add/remove participants. I'd > > appreciate it if anyone could add me to a wave on their server (I'm > > [email protected] for now). I'll probably try pulling the wave's > > history off your server a few times, but pulling seems to not work so > > I'd appreciate logs of any errors via email. That's optional > > though. :P > > > I can't just make a wave on my server because then other servers won't > > let me pull that wave's details back from it. > > > On Oct 20, 11:15 am, Morgan <[email protected]> wrote: > > > I have my own instance up at the moment with hopes of developing my > > > own backend code as time allows. > > > > [email protected] > > > > My own wave address on this instance is [email protected] > > > > - morgan > > > > On Oct 18, 7:26 am, Daniel Danopia <[email protected]> wrote: > > > > > I'm trying to write a custom provider, and it can successfully ping > > > > acmewave.com, but I'm having issues right now with testing the sending > > > > and receiving of messages. After lobbying in #googlewave and ##wave on > > > > freenode for a day, it seemed like no one runs Fedone anymore. Could > > > > someone please email/gtalk me at [email protected]? You could also post > > > > your wave address here so that other people who are trying to test out > > > > federation can add you. > > > > > Thanks! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Wave Protocol" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/wave-protocol?hl=en -~----------~----~----~----~------~----~------~--~---
