I really want to use Werkzeug as my framework(or anti-framework) for my
small business site but the barrier to entry is just too high for me.
I have been struggling to get started with Python web programming for
over 6 weeks now. I learned about Werkzeug fairly early on but passed by
it because I could not figure it out. After Django, Turbogears, CherryPy
and Pylons I am back to Werkzeug again. It makes a lot more sense now
but I needed the documentation from the other frameworks to understand
how a framework is put together.
I am a beginner. You would think that a beginner should start as simple
and as small as possible and then build on top of this. However with
Python frameworks the opposite seems to be true. It seem to me that
Django has the lowest barrier to entry due to the documentation, hosting
options and Django's own tools. However it also seems like the most
inflexible, most pre-configured, largest code base framework. It seems
like the beginner is forced to start big and just has to accept a poor
understanding of their own application.
I really like the minimalist approach that Werkzeug takes and I think in
the long run this would build a stronger foundation for a new web
programmer.
I registered www.pythonwebprogramming.org. Once I figure this all out, I
want to create a tutorial site to lower the barrier to entry for others.
My home based business is going through a tough time right now and I
don't have much money. However if someone wanted to put together an
end-to-end tutorial on getting started with Werkzeug I could sponsor
$100 U.S. I could post your tutorial on my site and hopefully I could
add my own tutorial someday soon.
Here are some topics I would like to cover.:
-What a framework is
-Where to get hosting for Werkzeug
-How to install Werkzeug
-How to set up the examples
-How to set up your own Werkzeug web App.
I can do some of these now but hosting is a big problem for me. I have
limited ISPs to choose from here in Canada. It is not easy to get a
static IP address in a residential area. I would love to know where I
could set up Werkzeug under shared hosting? It looks like Webfaction is
not an easy option. Has anyone tried a VPS?
Much of the code in the examples is self explanatory but more resources
on how to build your own Werkzeug App would help.
Again , I really believe in this project, please feedback your thoughts.
-Patrick
MilesTogoe wrote:
> Florian Apolloner wrote:
>
>> Of course you are right, the NameVirtualHost is in another file, so
>> the snippet doesn't include it. But my config works, just wanted to
>> show it to Miles.
>>
>>
> I appreciate your post, however, the webfaction shared hosting does not
> seem set up to do virtual hosting in that manner - the support team at
> webfaction was nice enough to get my config file working to serve up the
> .wsgi file. However, it was still not serving the the application or
> views file correctly and not showing any clues in the error file. I see
> the problem as trying to integrate 3 pieces - mod_wsgi, webfaction's
> hosting setup, and werkzeug. We are more application developers and not
> knowledgeable enough on sysadmin or wsgi to get this working without a
> real step by step tutorial which there seems none. And comments like
> "rtfm" on irc don't really help much. So at this point we're falling
> back to using Rails to have stuff running and will experiment with
> werkzeug/python as we can.
>
>
>
>
>> On Aug 17, 11:28 pm, "George Lambert" <[EMAIL PROTECTED]> wrote:
>>
>>
>>> are you missing a namedvirtualhost tag at the top of the apache config file
>>>
>>> if you are missing the declaraion at the top of the file the virtual
>>> host entry will not be processed.
>>>
>>> to access the script you will need to be using an http rquest that
>>> matches the named virtual host
>>>
>>> and if the virtual host is being used properly then there will be log
>>> entries in the virtual host specific access and error logs
>>>
>>> check that they have entries, and then post back the last few wlines
>>> of what is in them
>>>
>>> On 8/17/08, Florian Apolloner <[EMAIL PROTECTED]> wrote:
>>>
>>>
>>>
>>>
>>>
>>>> That's my full setup (on a test server):
>>>> <VirtualHost *:80>
>>>> ServerName staging.tld.eu
>>>>
>>>> WSGIDaemonProcess staging user=web group=web processes=2 threads=1
>>>> maximum-requests=500
>>>> WSGIProcessGroup staging
>>>> WSGIScriptAlias / /home/web/conf/apache/staging.wsgi
>>>>
>>>> <Directory /home/web/conf/apache>
>>>> # WSGIApplicationGroup %{GLOBAL} # Use this if running in
>>>> embedded mode and not in the process setup like I use in this example.
>>>> Order deny,allow
>>>> Allow from all
>>>> </Directory>
>>>>
>>>> </VirtualHost>
>>>>
>>>> On Aug 17, 8:29 pm, MilesTogoe <[EMAIL PROTECTED]> wrote:
>>>>
>>>>
>>>>> Florian Apolloner wrote:
>>>>>
>>>>>
>>>>>> Hi, You will need to open access for the directory containing the wsgi
>>>>>> file, eg (a really simple setup I am using...):
>>>>>>
>>>>>> WSGIScriptAlias / /home/web/conf/apache/app.wsgi
>>>>>>
>>>>>> <Directory /home/web/conf/apache> # this is the same dir as mentioned
>>>>>> by WSGIScriptAlias
>>>>>> Order deny,allow
>>>>>> Allow from all
>>>>>> </Directory>
>>>>>>
>>>>>> (Btw there is no need to have your wsgi files inside of your
>>>>>> ServerRoot). That's all what I can say now, without complete
>>>>>> description of your error or access to the necessary logfiles. See
>>>>>> http://code.google.com/p/modwsgi/wiki/ConfigurationGuidelinesformore
>>>>>> pointers. If you still can't enable it ping me on freenode (apollo13,
>>>>>> mostly on #pocoo too).
>>>>>>
>>>>>>
>>>>> Thanks, but the site still doesn't seem to be accessing the .wsgi
>>>>> file. A "recommended" directory structure and matching apache config
>>>>> example would be very helpful
>>>>>
>>>>>
>>>>>> On Aug 16, 8:40 pm, MilesTogoe <[EMAIL PROTECTED]> wrote:
>>>>>>
>>>>>>
>>>>>>> our setup on shared hosting is not working (we are getting mod_wsgi -
>>>>>>> but not pointing to our app)
>>>>>>> here is the apache httpd.conf
>>>>>>> ServerRoot "/home/user/webapps/ourapp/apache2"
>>>>>>>
>>>>>>> LoadModule dir_module modules/mod_dir.so
>>>>>>> LoadModule env_module modules/mod_env.so
>>>>>>> LoadModule log_config_module modules/mod_log_config.so
>>>>>>> LoadModule mime_module modules/mod_mime.so
>>>>>>> LoadModule rewrite_module modules/mod_rewrite.so
>>>>>>> LoadModule wsgi_module modules/mod_wsgi.so
>>>>>>>
>>>>>>> DirectoryIndex index.py
>>>>>>> DocumentRoot /home/user/webapps/ourapp/htdocs
>>>>>>> Listen 7061
>>>>>>> LogFormat "%{X-Forwarded-For}i %l %u %t \"%r\" %>s %b \"%{Referer}i\"
>>>>>>> \"%{User-Agent}i\"" combined
>>>>>>> CustomLog logs/access_log combined
>>>>>>> ServerLimit 2
>>>>>>> WSGIScriptAlias / /home/user/webapps/ourapp/ourapp.wsgi
>>>>>>>
>>>>>>> <Directory /home/user/webapps/ourapp/htdocs>
>>>>>>> AddHandler wsgi-script .py
>>>>>>> </Directory>
>>>>>>>
>>>>>>> and here is ourapp.wsgi file
>>>>>>> from ourapp import models, utils
>>>>>>> from ourapp.application import OurApp
>>>>>>> application = OurApp('sqlite:///ourapp/ourapp.db')
>>>>>>>
>>>>>>> any thoughts why it's not working correctly ?
>>>>>>>
>>>>>>>
>>>
>>>
>>>
>>
>>
>
>
> >
>
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"pocoo-libs" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/pocoo-libs?hl=en
-~----------~----~----~----~------~----~------~--~---
