oops, meant to send this to the list before:

Seems it was an embarrassingly simple problem for the PHP version - I
had "AllowOverride None" set up on this server so the .htaccess wasn't
being read.

Still haven't had any success with the Java version, but recent SVN
updates have changed the warnings/errors I'm getting dramatically so I
guess I may have just checked out at a bad moment?

I've run "mvn", which is supposed to take care of cleanup, packaging and
installing, and tried each stage manually but with the same response.
I'm on Sun's JVM:

java version "1.6.0_0"
OpenJDK 64-Bit Server VM (build 1.6.0_0-b11, mixed mode)


We're unlikely to want to modify much, so language isn't much of an
issue - we do just need the gadget server without the social parts.


Tim

On Fri, 2008-10-17 at 11:34 -0700, Kevin Brown wrote:
> On Fri, Oct 17, 2008 at 5:36 AM, Tim Wintle
> <[EMAIL PROTECTED]> wrote:
>         Hi, completely new to Shindig,
>         
>          * I'm interested in the gadget server rather than the social
>         server
>         part of the system - is there anything I should be aware of
>         about
>         running the gadget server without any social support?
>         
>          * We don't use Java or PHP very much, so there's no obvious
>         choice for
>         which to use. Which would be most recommended? Our use case
>         would mean a
>         high volume of hits on a low number of different gadgets per
>         day, so I
>         guess good caching of external data is important, although
>         ease of
>         set-up and maintenance would be the most important.
> 
> They're pretty much identical when it comes to features and
> performance. The java renderer implements a few more experimental
> things (proxied rendering and support for the caja project), but
> otherwise there isn't much of a difference other than set up and
> configuration. 
> 
> For PHP you need to:
> 
> - Install and configure Apache (or other PHP-capable web server)
> - Install and configure PHP for your web server
> - Configure and deploy shindig code
> 
> For Java you have to:
> 
> - Build the code (we'll have prebuilt jars soon, but for now the
> instructions on http://incubator.apache.org/shindig are required)
> - Install and configure a servlet container (tomcat, jetty, etc.)
> - Configure and deploy shindig code
> 
> From personal experience, I think deploying PHP is easier than
> deploying java but you may feel differently. I'd pick a version based
> on what language you're more likely to want to write actual code in,
> though, since if you want to do tight integration with an existing
> social data backend you'll probably have to write your own adapters in
> either language.
> 
> 
>         
>         
>          * I'm having troubles running either version at the moment.
>         
>         *******
>         Java version:
>         *******
>         "mvn" runs fine, I get six warnings but no errors.
>         
>         "mvn -Prun -PrunType=gadgets" Starts Jetty, but gives the
>         errors:
>         
>         """
>         
>            2008-10-17 13:18:07.841::WARN:  Web application not found
>         [path]/java/server/target/shindig-server-1-SNAPSHOT.war
>         2008-10-17 13:18:07.841::WARN:  Failed startup of context
>         
>         [EMAIL 
> PROTECTED]/,[path]/shindig/java/server/target/shindig-server-1-SNAPSHOT.war
> 
> Did you run mvn install and mvn package before mvn -Prun ? -Prun
> starts the server, but since it hasn't been built yet (see previous
> comment), you have to build first. 
> 
> 
>         
>         
>         """
>         
>         and then I get 503s from the actual server (which I guess is
>         to be
>         expected)
>         
>         *******
>         PHP version:
>         *******
>         Apache is configured fine, but what is "ifr" supposed to be
>         pointing to?
>         I'm just getting a 404 when I visit the test url. I don't know
>         what
>         other urls there are to hit to try to test the server.
>         
>         Thanks,
>         
>         Tim Wintle
>         
>         
>         
>         
>         
>         
>         
>         
> 
> 

Reply via email to