I've been moving forward with the django server option and have come across an oddity: while I can access my site on the resident machine via http://localhost:8000, if I try to access it from another machine on the network via http://10.0.0.66:8000 I get an error in my browser:
Failed to Connect Though the site seems valid, the browser was unable to establish a connection. If I can get this problem resolved, then I've found my lowest barrier solution. Any thoughts? Is there something baked into the django server that prevents one from accessing it via a remote machine? If I can't find a solution, I'll look into lighthttpd. Cheers, Kevin On Apr 21, 12:46 pm, Oli Warner <o...@thepcspy.com> wrote: > You could, but as you say you would have to script it to daemonise. > > If resources are what's putting you off running something like Apache, you > should know there are plenty of lightweight servers that are simple to get > up and running, even on desktop machines. > > Just to state my position: I would find it easier to install something like > Lighttpd, Nginx or Cherokee but that's because I have experience with all of > them. If you can get the dev server to auto-load, I can't see any real > reason stopping you from going that route. It's not a bad server and I doubt > you'd see any performance/resource issues for fewer than 10 people using it. > > And of course, there's nothing stopping you from starting off on the dev > server and moving up if you find you need to. It only takes a couple of > well-crafted googles, a little reading and a few keystrokes to get a real > server running yout site. > > On Tue, Apr 21, 2009 at 8:18 PM, Kevin Audleman > <kevin.audle...@gmail.com>wrote: > > > > > I'm building a tool for a client that synchs email addresses between > > systems and decided to use the excellent django framework because it > > gives me a quick and powerful connection to a database back-end and > > the ability to provide a web front-end for the users. I'm trying to > > decide if it's worth going through the trouble of setting up Apache to > > serve the program or if I can safely get away with using django's > > server. Here are the details. > > > This program will reside on an in-house server and will not be > > accessible by the public. There will only be one user at a time. The > > program will likely run once or twice a day, at which point it will do > > some light interaction with MySQL. It will also be available at all > > times to staff via their web browser (and an internal IP address) > > should they wish to check a log of previous transactions. > > > My instincts tell me I can get away with using the test server, as > > what I'm doing is hardly a web application that needs to deal with > > thousands of transactions. I imagine I could just set up a startup > > script in OS X to launch the django server at startup and leave it > > running. > > > Any advice -- either saying yes this is a good idea or no there are > > serious drawbacks to this approach -- greatly appreciated! > > > Cheers, > > Kevin --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@googlegroups.com To unsubscribe from this group, send email to django-users+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
