Web2py is "full stack" Python Web Framework, Lighttpd is fast, multi-threaded HTTP server. I'll present a method to connect web2py-based application under lighttpd.
I assume the following setup is already done:
- A domain named "myapp.com" is configured to point to your server
- Python / lighttpd is already installed on server
- Your web2py app is placed under /var/www/web2py
- Your web2py app has application "myapproot" configured
First of all, you have to configure lighttpd to locate web2py application, create file /etc/lighttpd/conf-enabled/myapp.conf:
Web2Py is a full-stack Python web framework that can be compared to Django, but is easier to learn due to convention-over-explicit-statement preference. In this article I'll check how static verification techniques developed by me for many different environments (JSP, Django templates, TAL, …) can be applied for web2py environment.
Static verification means locating simple bugs without running application thus very high (>95%) testing coverage (and high related cost) is not required. Instead with trying to cover by tests every possible screen/workflow/code line/… we can scan all codebase and search for some constraints. Most of them (based on my experience) are static – do not depend on runtime data thus can be effectively checked without running an application.
I've been using many different Python Web Frameworks so far:
All frameworks have its strengths and weakness. For new project that will handle appointments using existing calendar I decided to give web2py a try, rationale:
- all stuff included on board, no manual integration of 3rd party libraries
- stable API
- small and elegant
- integrates with GAE (with subset of DB layer)
- template selection separated from controller (easier unit testing)
- easy template syntax (reuses Python code embedded into markup language)
After first phase of product I'll report if my expectations above were correct and what kind of problems were located (if any).