There is a typo, try this: http://svn.apache.org/repos/asf/james/server/trunk/
On Feb 1, 2015, at 5:01 PM, Chris Means <cme...@intfar.com> wrote: > Robert, > > What's the correct/current URL to use for James? > > This is what is in your video (if I'm reading it right): > > http://svn.apache.org/respos/asf/james/server/trunk/ > > But, the page doesn't exist. > > -Chris > > -----Original Message----- > From: Chris Means [mailto:cme...@intfar.com] > Sent: Saturday, January 31, 2015 8:52 PM > To: 'James Users List' > Subject: RE: Minimum Platform Requirements? > > Great. Thanks! > > -----Original Message----- > From: Robert Munn [mailto:robert.d.m...@gmail.com] > Sent: Saturday, January 31, 2015 8:49 PM > To: James Users List > Subject: Re: Minimum Platform Requirements? > > Probably then your best course is to set up a test and see if James can run > with -Xmx=64m or -Xmx=128m, which is maybe the max you are going to be able > to dedicate to the application unless you have stripped the OS install down > to the bones. If you decide to give it a try, please post your findings back > to the list for others' benefit. If you want to run James, I suggest > building it from source. There is a post on my blog here: > > http://blog.bonnydoonmedia.com/post.cfm/video-building-apache-james-with-ecl > ipse > > That links to the Youtube video instructions, and Bernd Waibel has provided > some written instructions for the build process, also linked from my blog, > here: > > http://blog.bonnydoonmedia.com/post.cfm/walkthrough-tutorials-compiling-apac > he-james-v3-with-eclipse > > > > On Jan 31, 2015, at 6:25 PM, Chris Means <cme...@intfar.com> wrote: > >> Thanks Robert. >> >> I'm on an rPi kick at the moment, and want the flexibility to >> re-task/mix tasks for the devices, so keeping them all the same (core) >> will make it easier for me at the moment. >> >> I'm still learning my way around Linux, so keeping to Raspbian will >> also help. >> >> -Chris >> >> -----Original Message----- >> From: Robert Munn [mailto:robert.d.m...@gmail.com] >> Sent: Saturday, January 31, 2015 6:45 PM >> To: James Users List >> Subject: Re: Minimum Platform Requirements? >> >> I don't know about James v2 versus v 3, but in my experience 512 MB >> RAM would be a pretty minimal environment for any Java server app. >> >> If what you want is a small, low-power appliance-type device, have you >> considered an Atom-based SFF PC? You can pick up a used Asus eeeBox >> with HDD, 2GB RAM, and Windows 7 for not much more than a Raspberry >> Pi. I've been using one of them as an entertainment PC for a few >> years, they are small, quiet and consume very little power. Asus, >> Zotac, and many other brands offer these machines, and they are in >> good supply new or used. If you keep it on Windows, you can upgrade to >> 4GB > RAM for ~ $15. >> >> Robert >> >> >> >> On Jan 31, 2015, at 10:21 AM, Chris Means <cme...@intfar.com> wrote: >> >>> Hi, >>> >>> >>> >>> I'm a James User/Developer from many, many moons ago. >>> >>> >>> >>> I've been running James v2.2 w/MySQL on an old WinNT device that I'm >>> planning on decommissioning. My hope is that I can migrate to a >>> Raspberry Pi B+.I've not found much on this sort of deployment on the > web. >>> >>> >>> >>> I only have a few users (5 - 10), so there's not a lot of traffic >>> (mostly Junk email). >>> >>> >>> >>> Is the rPi a reasonable platform? It only has 512MB RAM, which I >>> assume will be the primary constraint.though I also believe that >>> using MySQL will off-load some of the memory issues for James. >>> >>> >>> >>> Any thoughts? >>> >>> >>> >>> Should I aim for trying James v3, or go to what's stable in v2? >>> >>> >>> >>> Any migration issues for MySQL I should be aware of? >>> >>> >>> >>> Thanks. >>> >>> >>> >>> -Chris >>> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org >> For additional commands, e-mail: server-user-h...@james.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org > For additional commands, e-mail: server-user-h...@james.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: server-user-unsubscr...@james.apache.org For additional commands, e-mail: server-user-h...@james.apache.org
