i
On Feb 22, 8:01 pm, cadrentes <cadren...@gmail.com> wrote:
> Thanks so much for your response.
>
> I've followed the instructions but it is unclear to me how to (from
> pg. 52)..."By default,
> web2py runs the web server on 127.0.0.1:8000 but, you can run it on
> any
> available IP address and port..."
>
> When I start web2py I get:
>
> default applications appear to be installed already
> web2py Enterprise Web Framework
> Created by Massimo Di Pierro, Copyright 2007-2009
> Version 1.56.3 (2009-02-16 10:07:09)
> Database drivers available: SQLite3
> ...
> please visit:
> http://127.0.0.1:8000
If you start web2py from the command line:
% python2.5 web2py.py
you will get these messages (on Linux you would have been asked to
create an admin password).
% python2.5 web2py.py --help
will show you options. If you tell web2py which port you want it to
run on, for example:
% python2.5 web2py.py -p 80
then web2py will make a file with startup parameters, and use them
next time on that port - the parameter files look like:
parameters_8000.py or parameters_80.py.
Whenever you run web2py this way from the command line, web2py is
using it's built-in webserver (cherrypy).
Once you create your default parameters, when webpy starts from
Apache, it will read the parameters for the port that it is started
under, and you're all set - you want to create a parameters file so
that you will start up the way you intend under apache.
For running under apache, you'll want to use mod_wsgi. For example,
instructions for setup on webfaction appear here:
http://forum.webfaction.com/viewtopic.php?pid=8473
Since there are several ways to setup Apache to run mod_wsgi, and
then several ways to configure mod_wsgi, there will be differences in
the setups you. For mod_wsgi, I suggest you read up (http://
code.google.com/p/modwsgi/ and http://groups.google.com/group/modwsgi
), then try some existing setup and work from there. With wireshark
(http://www.wireshark.org/) you can filter just http packets; with
that, and Apache logs you can put together what is going on with your
setup, and unravel any problems pretty readily.
If you're going to run for yourself on Ubunto, you can just run the
built-in cherrypy server; you can play with and sort out your Apache
configuration that you'd want. If you're working on a hosted
location, they are usually very knowledgeable with their setups, and
all you need to know is more-or-less what is going on w/ web2py (logs
and wireshark will help).
Hope this is helpful.
Regards,
Yarko
>
> I've purchased a copy of the manual from lulu and find it very clearly
> written. Thanks for all your work!
>
> On Feb 22, 9:37 am, mdipierro <mdipie...@cs.depaul.edu> wrote:
>
> > Welcome.
>
> > your Apache is not running web2py.
>
> > You need to setup mod_proxy (easy) or mod_wsgi (difficult but better
> > for production).
>
> > I suggest you download
>
> >http://mdp.cti.depaul.edu/examples/static/web2py_manual_cut.pdf
>
> > for deployment instructions. Let us know if you have problems and we
> > will help.
>
> > Massimo
>
> > On Feb 22, 10:09 am, cadrentes <cadren...@gmail.com> wrote:
>
> > > Linux user: 2 yrs
> > > Web2py user: 2 days
>
> > > I don't know how to phrase this problem. I'm trying to set up a
> > > server. I get thishttp://65.49.60.137/whenfollowingthe
> > > instructions in the guide instead of the html.
>
> > > Any ideas?
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"web2py Web Framework" group.
To post to this group, send email to web2py@googlegroups.com
To unsubscribe from this group, send email to
web2py+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/web2py?hl=en
-~----------~----~----~----~------~----~------~--~---
