Partial answers inline:

On Monday, February 9, 2015 at 12:52:04 PM UTC-8, web2py user wrote:
>
> I have Python, Web2py and various database technologies installed on an 
> Linux server (say 123.45.67.89). Assuming I've configured my application, 
> databases, and folder permissions properly, is deploying my Web2py 
> application as simple as launching Web2py (the command on my machine would 
> be python web2py.py in /dir1$), setting the server IP to 'public 
> 0.0.0.0', and visiting 123.45.67.89? 
>
> How does what I'm describing differ from what the following does (from 
> Linux / Unix section of 
> http://www.web2py.com/books/default/chapter/34/13/deployment-recipes):
>
> wget http://web2py.googlecode.com/hg/scripts/setup-web2py-ubuntu.sh
> chmod +x setup-web2py-ubuntu.sh
> sudo ./setup-web2py-ubuntu.sh
>
>
> This part of the recipe precedes the start up of web2py.

Specifically, the *wge*t fetches a script for the ubuntu deployment.  The 
*chmod* tells the system that the script should executable.  The *sudo* 
says "give me the power to run this script, which touches things in special 
places".  The script then does something to prepare for web2py startup.  
The *sudo* will not work if you haven't been granted the privileges 
involved; that is usually done by the person who sets up the server or the 
server administrator.

I don't have a lot of experience deploying applications or working with 
> Apache, so I don't really understand the differences between what I'm doing 
> and the deployment recipe, nor do I really understand what's being 
> described in the *Apache or mod_wsgi setup* sections. Furthermore, when I 
> attempt to run the code above I just receive a bunch of errors (no sudoers, 
> files / directories don't exist, etc). 
>

Apache is a server interface that makes web sites visible to the world.  It 
takes care of listening to the actual ports and passing requests to the 
actual server code for a particular site.  It is capable of supporting 
several sites on a single host, and the setup in the deployment recipe is 
for telling Apache how to connect the incoming requests to the server(s).  
Web2py is a server that Apache would pass requests to.

I have not done such a deployment.  I run in a VM (under VmWare on a local 
hardware host), but I use the built-in Rocket server rather than Apache or 
Nginx.  And I downloaded the binary installation; the deployment script may 
expect a source installation.

However, there are plenty of people who do run on virtual hosts.  I don't 
remember that Bluehost has been mentioned.  I think Blue Ocean has, but 
PythonAnywhere and Google Apps Engine seem to be the most popular.  There 
have been some people using OpenShift, Heroku, and some others.   I by the 
subject list someone is trying Azure.  You can browse the group archives 
(you can use any of the above for a search term; you might also try 
"virtual host" or "hosting service".) to find previous discussions  and how 
particular problems needed to be solved.

 

> Thanks so much for the help. Just want to make sure I know what's going 
> on, the limitations / differences, etc., especially given the fact that 
> rapid deployment isn't working for me. If you have any decent references 
> that you could point me to, I'd be glad to read them as well. 
>
> Not sure if it helps, but I'm attempting to deploy on Bluehost with a 
> dedicated IP. Deploying a Django app was a piece of cake on Bluehost, so I 
> hope I'm close. 
>
I haven't done a Django deployment, either, so I can't compare.  But if you 
don't have the privileges you need, you can expect frustration.  If Linux 
is a new environment for you, you might want to have someone local you can 
get coaching from.

Hope this helps, although I know I'm doing a lot of hand-waving rather than 
giving detailed answers or step-by-step instructions.

/dps

 

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to