Sure. Thanks for having a look #!/bin/bash
# Configuration for the FedOne run scripts. # # Copy this file to run-config.sh and configure the variables there. # Please see http://code.google.com/p/wave-protocol/wiki/Installation for # instructions on how to configure the flags. # ### Variables common to the server, clients, and agents ### # Domain name of the wave server WAVE_SERVER_DOMAIN_NAME=1011ltd.com # Host name and port the wave server's client frontend listens on WAVE_SERVER_HOSTNAME=1011ltd.com WAVE_SERVER_PORT=3456 # The version of FedOne, extracted from the build.properties file FEDONE_VERSION=`grep ^fedone.version= build.properties | cut -f2 -d=` ### Server-specific variables ### # These will probably need to be changed XMPP_SERVER_SECRET=******** PRIVATE_KEY_FILENAME=../certs/${WAVE_SERVER_DOMAIN_NAME}.key CERTIFICATE_FILENAME_LIST=../certs/${WAVE_SERVER_DOMAIN_NAME}.crt,../certs/sub.class1.server.ca.pem,../certs/startssl.pem # These should be okay to leave alone CERTIFICATE_DOMAIN_NAME=$WAVE_SERVER_DOMAIN_NAME XMPP_SERVER_HOSTNAME=$WAVE_SERVER_DOMAIN_NAME XMPP_SERVER_PORT=5275 #XMPP_SERVER_PING=acmewave.com XMPP_SERVER_PING=wavesandbox.com # Set XMPP_SERVER_IP to localhost if the XMPP and FedOne servers are # running on the same host XMPP_SERVER_IP=$XMPP_SERVER_HOSTNAME # Set true to disable the verification of signed deltas WAVESERVER_DISABLE_VERIFICATION=false # Set true to disable the verification of signers (certificates) WAVESERVER_DISABLE_SIGNER_VERIFICATION=false On Fri, Jan 29, 2010 at 10:07 PM, James Purser <[email protected]>wrote: > On Sat, Jan 30, 2010 at 6:20 AM, [email protected] > <[email protected]>wrote: > >> Hi >> >> My wave federation setup is (I hope) almost working, but there are >> some problems which I think are related. >> >> Here's the scenario: >> 1. The wave server is running on 1011ltd.com, connected to Openfire >> 2. I create a new wave in the sandbox and add '[email protected]' >> to the wave.... no incoming messages in the open server console. >> 3. I create a new wave in the sandbox and add 'bjnort...@wave. >> 1011ltd.com' to the wave... and I can see the incoming deltas. >> >> I should be able to add someone from the sandbox without the 'wave.' >> bit, correct? >> >> Then there's some weird interaction if I have the console running as >> user 'bjnortier'. When I create a wave in the sandbox and add >> '[email protected]', nothing happens in the console, but when I >> also add '[email protected]', the wave shows up in the >> console and I can reply. The user that has replied shows up as >> '[email protected]' >> >> I cannot create a wave in the console and see it in the sandbox, but >> I'm hoping these problems are related. >> >> Any ideas? >> >> I can post the logs if that will help... >> Thanks! >> Ben >> >> > Could you post your run-config.sh? > > -- > James Purserhttp://wavingtheshiny.collaborynth.com.au > Wave Addresses: [email protected] > (wave.google.com)[email protected] > (wavesandbox.com)[email protected] (collaborynth.com.au FedOne Server) > Skype: purserj1977 > GTalk: [email protected] > > > > -- > 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]<wave-protocol%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/wave-protocol?hl=en. > -- Benjamin Nortier e: [email protected] c: +44 (0)778 946 1959 gtalk: [email protected] -- 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.
