1. Not relevant for web2py. The file structure is enforced by the framework
2. There is a web2py-celery but needs work. There is also the built-in
web2py scheduler. In many situation it is sufficient. And it is in the box.
celery pro: faster communication between master and workers
scheduler pro: workers see same environment as web2py controllers
3. Yes. Use gunicorn or nginx, instead of Apache. (*)
4. Don't be afraid of MongoDB. DAL supports it. Yet of 99% of the cases
PostgreSQL does what you need. If you use DAL you have a choice and both
suport the 'json' type.
5. Use named url and reverse. You already do this in web2py all the time.
The {{=URL(...)}}.
6. web2py has no settings.py so nothing to see here.
7. Use supervisor for process monitoring. (*)
8. Use Ajax (*)
9. Use Redis (*) web2py provides
gluon/contrib/redis_cache.py
gluon/contrib/redis_session.py
10. Use munin and statds for process monitoring. (*)
11. Use jammit for static asset compression (*) Yet web2py has buil-in
static asset management as well as
response.optimize_css = 'concat,minify,inline'
response.optimize_js = 'concat,minify,inline'
(*) Not Django or web2py specific.
On Monday, 22 April 2013 01:52:55 UTC-5, encompass wrote:
>
> How we we fit in all of this?
> https://medium.com/cs-math/f29f6080c131
>
--
---
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
