On Mar 15, 1:34 pm, solom <gawaher....@gmail.com> wrote:
> > You can certainly develop your program locally just fine.
> > When you want to upload it to your server you still need a web2py setup
>
> Is there any way I can just use web2py locally to create an
> application, then somehow compile my application into a website that
> consists of .py files only (or any files that python can run), so that
> it can be uploaded to a web folder in my hosting account, without
> having to depend on a web2py setup in the sever?

This seems to be a fundamental question.

Perhaps look at http://www.web2py.com/book/default/section/1/6
and read section 1.

In general, this will be the same kind of information with most _any_
web app server (not just web2py, not just python; for example, look at
http://www.playframework.org/documentation/1.0.1/overview, or
http://docs.djangoproject.com/en/1.1/intro/overview/#intro-overview)

Some frameworks do less, are lightweight, and leave more to you to do
(http://werkzeug.pocoo.org/ perhaps; a simple HTML page, or text shown
in a browser is perhaps a decay to the most straightforward);
Some structure the big picture of the solution for you more (e.g.
http://plone.org/);

But the underlying question you ask is fundamental about the current
structure of web-based applications in a TCP/IP world.
Draw a map out of the "territory" (literally - Massimo had a nice map
in his early book of calls and how they from thru web2py; maybe he can
point us to it)...

Then you will see you are asking this sort of question:

- I want to share information on the web;
- I want it to be dynamic (i.e. a static html page & page editor won't
do);
- I do _not_ want to have to do all it takes on my own (e.g. just
write my own dynamic web app, with no more pre-existing support &
structure than simply Python provides);
- I therefore have to choose an appropriate "sweet spot" - a framework
that provides the level of support for my work (so I have less to do)
and lets me quickly and flexibly accomplish what I want with minimal
work.
- Regardless of _how_ I choose to go, I will have to understand web
application deployment (for even for a static HTML page, I have to
somehow serve it);

Have fun - work locally;  then deploy to your web service provider
with their help (i.e., start with "canned" or pre-scripted solutions
so you have less to worry about at first).

Regards,
- Yarko

-- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To post to this group, send email to web...@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.

Reply via email to