Hi Folks!
Here's how I've solved the problem:
I'm now running a web2py local server with regular configuration:
nohup python web2py.py -i 127.0.0.1 -p 8000
Then configured apache2 based on the alternative "mod_proxy" configuration
described in http://web2py.com/book/default/chapter/13.
NameVirt
If your app is proxied you might be running into an apache config issue.
See the following:
https://bugzilla.redhat.com/show_bug.cgi?id=843326
&
https://github.com/rmillner/crankcase/commit/58f582172a43c118e8610b023853945dd01cc7ca
The used the following to make sure the correct wsgi param is se
The method depends on which web server are you using. Which one are using?
General guidance can be found in book, chapter 13
http://web2py.com/book/default/chapter/13
On Thursday, September 13, 2012 8:38:45 AM UTC-5, Francisco Barretto wrote:
>
> Hi There!
>
> Deploying web2py on a server
why don't you just enable remote forwarding if you don't want to setup the
SSL on the webserver ?
if you can log in with ssh, you should be able to do:
ssh -L local_port:local_ip:remote_port username@address
This, in addition to login to the ssh shell, will redirect the services
listening on t
4 matches
Mail list logo
