[web2py] Re: Web2Py + VueJS SPA (Webpack)
Hi Massimo, I thought you might be interested in this:
https://bootstrap-vue.js.org/
Quite a new project, MIT license, currently under very active development
mainly by a Canadian and an Iranian.
On Tuesday, November 14, 2017 at 12:36:52 PM UTC-7, 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.
[web2py] Re: Future of web2py
According to github, there were semi-regular releases going back to 2013, then they stopped about a year ago, so I guess it's only natural for people to wonder about the status of the project. Personally, I'm wondering if the project will continue to build production releases in the future. I see that master still gets some love, so maybe master is now stable for production and I missed it? Anyhow, thank you for all your work on this framework. I admire the project itself and I think the community speaks for its integrity. I read your post earlier in this thread on your plans for web3py, and I thought I would say that as a web2py user, I loved how it gave me a current version of a few nice libraries and flattened web development into a single Python layer. Basically it gave me a mostly pre-built good-enough web interface and let me get on with the business of developing services for users. Your web3py post concedes that the days of the flat development stack are over, and I agree it's unavoidable to use some of the newer JS components and move a lot of the work to the browser. I haven't checked out the stack you've listed in your reply yet, but I'll very likely end up using whatever you put together because I want to keep using helpers, validators and the DAL. I look forward to the day the lineup is stable enough for release, and thanks again for your past work on web2py. On Friday, June 2, 2017 at 2:59:12 PM UTC-6, Massimo Di Pierro wrote: > > OK course it is still maintained why do you ask? > > On Wednesday, 31 May 2017 14:21:40 UTC-5, Oasis Agano wrote: >> >> >> But web2py is still maintained right? or we start buying flask books >> On Saturday, May 27, 2017 at 9:11:02 AM UTC+2, Andrea Fae' wrote: >>> >>> Hello guys, >>> I'd like to know if there will be future of web2py? Any information >>> about it? >>> Thanks >>> >> -- 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.
