I believe that strongest web2py's feature is that it allows to do the stuff by one developer, as if it would be done by several qualified one's. You are going to make web2py's fans to code in pure JS to develop frontend, right? I think it is not the future that's expected. My dream is web2py integrated with rapydscript/rapydscript-ng + rapydml + lib of vue-components(written on rapydscript) - it would be really fantastic.
On Tuesday, November 14, 2017 at 10:36:52 PM UTC+3, Massimo Di Pierro wrote: > > This is fantastic. Thank you Carlos, > please email me personally about you work. I think this is the path to the > future of web2py. > > On Tuesday, 14 November 2017 10:48:03 UTC-6, Carlos A. Armenta Castro > wrote: >> >> I have using Web2Py for too many years for commercial websites and for >> Intranets in México, I want to say that Web2Py is an AMAZING Framework!!! >> For my new project I need to use an SPA VueJs + Webpack for the FrontEnd >> ( http://quasar-framework.org/ ) and a Web2Py as my BackEnd API Server. >> I'm curious about to integrate his two web frameworks using web2py routes >> to serve this two apps in the same port but different URL. >> >> Example: >> http://127.0.1.1/welcome/api ---> My Web2py API Controller >> http://127.0.1.1/welcome ---> My VueJS APP with webpack ( >> http://quasar-framework.org/ ) <-- Pointing to index.html in *dist/ * >> and permit to use all the static files deposited in the same path >> *dist/** >> >> *VueJS + Webpack APP Structure* >> >> ├── *dist/ * *# Compiled APP (Serve this files as the >> static SPA)* >> │ *└── index.html >> │ ├── fonts/ >> │ │ └── ... >> │ ├── static/ >> │ │ └── ... >> │ ├── js/ >> │ │ └── ...* >> ├── config/ >> │ ├── index.js # main project config >> │ └── ... >> ├── src/ >> │ ├── main.js # app entry file >> │ ├── App.vue # main app component >> │ ├── components/ # ui components >> │ │ └── ... >> │ └── assets/ # module assets (processed by webpack) >> │ └── ... >> ├── static/ # pure static assets (directly copied) >> ├── test/ >> ... >> >> Actually I am doing this work in my NginX Server but I Will be happy if I >> can do the same thing easily using pure web2py!!!! >> >> Why using the same port? Because the CORS issues, this is the best and easy >> way to deal with CORS. I know I can use sub-domains in the same port, I know >> I can use ALLOW ORIGIN headers in W2P side but that are not options for me >> in this case. >> >> NginX config working: >> >> location / { >> index index.html index.htm; >> root /home/www-data/vue/applications/simott; >> try_files $uri $uri/ /index.html; >> } >> >> location /api { >> uwsgi_pass unix:///tmp/web2py.socket; >> include uwsgi_params; >> uwsgi_param UWSGI_SCHEME $scheme; >> uwsgi_param SERVER_SOFTWARE nginx/$nginx_version; >> >> } >> >> Any recommendations? Thanks in advance! >> >> -- 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.
