Keep in mind you can use web2py as a CAS server and you can wipe out most
things you don't need in Web2py, creating a minimum environment. ;-)
On Tue, 17 Mar 2015 11:02:12 -0300 Júlia Rizza wrote
Jorge, since the front-end migrated to Angular and decided to do most of the
app
In fact in order to use proper sessions in Flask you need sqlalchemy.
Flask+SQLAlchemy contains more code than web2py without
admin/examples/welcome app.
Flask is faster on hello world apps but the difference washes out as soon
as you access storage server side.
Massimo
On Thursday, 19
Thank you for your help. I'll think in a better way to check the passwords
then, maybe using the web2py version as an API until most of the users
changed their passwords.
Em segunda-feira, 16 de março de 2015 19:45:40 UTC-3, Niphlod escreveu:
uhm. web2py's format means 1000 iterations and 20
Jorge, since the front-end migrated to Angular and decided to do most of
the app services on his side, I just wanted to use something smaller and
simpler, like a micro-framework, considering that I wouldn't need most of
the web2py tools. Nothing particular with the framework, just a personal
Just be aware of one thing. Flask by default stores sessions in cookies.
They have a limit of 4K. This means sessions get corrupted or disappear if
you have large sessions or other cookies from the same domain. So if you
need sessions I recommend you store them in db.
Massimo
On Tuesday, 17
why did you choose to migrate to flask?
On Monday, March 16, 2015 at 4:38:40 PM UTC-5, Júlia Rizza wrote:
Hello,
I'm migrating an app from web2py to Flask and I want to use Werkzeug
Security to manage the users passwords, but there is a conflict between the
passwords hashes of web2py and
uhm. web2py's format means 1000 iterations and 20 chars length, with sha512
as hash function.
the missing variable here is 20 char length... iterations are the
same (1000) and so the hash function (sha512).
from werzeug docs, it seems that the key length is the digest size...which
for
7 matches
Mail list logo
