Thank you, Anthony!
I deploy the app using commandline script which packs the application
sources, uploads them on server and calls a server-side script which
compiles the app.
So, on the server side in the application folder I have standard
directory structure - source files in 'models', 'controllers', 'views',
and the compiled version in the 'compiled' subfolder.
But it seems to me, that WSGI can work only with compiled files, not
with the sources.
Regarding your patch - IMO compilation gives sense even if the whole app
can't be packed compiled (performance). It could even allow "mixed"
packing - add compiled files for all compilable content and sources for
the remaining noncompilable views.
David
On 22.7.2015 15:44, Anthony wrote:
Probably you chose "Pack compiled" in admin, which packs only the
compiled models, controllers, and views. If you didn't compile the
views, then your packed app will have no views. Instead, choose "Pack
custom", and be sure to include the /views folder.
A while back, I submitted a patch that would allow you to compile the
whole app, even if some particular views could not be compiled. In
that case, you could still benefit from compiling most of the views.
However, the patch was never applied. If this is of interest to you,
maybe submit an issue on Github and link to
https://groups.google.com/d/msg/web2py-developers/GhvqakUaujA/iTj0_uP76XcJ.
Anthony
--
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.
